GET
/api/fetchQuestions
Try Me!
Query Parameters
Response Schema
| Field | Type | Description |
|---|---|---|
| questions | array | A list of environmental questions for the given industry |
Summary
Returns a list of questions given industry
This endpoint is designed for read-only access and is commonly used by client applications to populate selectors such as dropdowns, filters, and search facets.
Description
The Fetch Questions API retrieves question records from the database and returns them as a JSON array.
Key characteristics of this endpoint:
- Publicly accessible (no authentication required)
- No query parameters or request body
- Database identifiers (
_id) are excluded from responses - Empty results are treated as a valid, non-error response
- Clear separation between database errors and unexpected server failures
This endpoint serves as the authoritative source of question data across the platform.
Endpoint
GET /api/fetchQuestionsRequest
This endpoint accepts a singular parameter: industry
Parameters
| Parameters | Required | Description |
|---|---|---|
industry | mandatory | The industry whose questions are needed |
Headers
This endpoint accepts one parameter
| Header | Required | Description |
|---|---|---|
Accept | Optional | Defaults to application/json |
Response Schema
Success - 200 OK
string[]Example Response
[
"Helloabc",
"Helloabc"
]Empty Response
If the questions or industry does/do not exist, an empty array is returned:
[]Error Codes & Response Types
503 Service Unavailable
Returned when the database is temporarily unavailable, or a query fails due to a database issue
Response Body
{
"detail" : "Database temporarily unavailable"
}Typical Causes
- MongoDB Connection Issues
- Database timeout or query failure for a non-general reason
500 Internal Server Error
Returned when an unexpected server-side error occurs.
Response Body
{
"detail" : "Internal server error"
}Typical Causes
- Unhandled runtime exception
- Application-level failure outside database operations.
Implementation Notes
- Uses a MongoDB find() query with projection to exclude _id
- Materializes the cursor before returning the response
- Logs both database-specific and unexpected errors for observability
- Treats empty datasets as a valid state, not an error condition