Http Status Overview
| HTTP Status Code | Description | Content Returned |
|---|---|---|
| 200 (Success) | Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action. | Application response block as defined by the application Swagger document. |
| 206 (Partial Content) | The HTTP 206 Partial Content success status response code indicates that the request has succeeded and the response body contains a subset of available data. The content-range response header indicates the range of data that was returned which can be used to set the offset on subsequent requests to obtain additional data. | None |
| 400 (Bad Request) | General error when fulfilling the request would cause an invalid state. Domain validation errors, missing data, etc. are some examples. | Standard error response block as defined here. |
| 401 (Unauthorized) | Error code for a missing or invalid authentication token. | None |
| 403 (Forbidden) | Error code for user not authorized to perform the operation, doesn't have rights to access the resource, or the resource is unavailable for some reason (e.g. time constraints, etc.). | None |
| 404 (Not Found) | Used when the requested resource is not found, whether it doesn't exist or if there was a 401 or 403 that, for security reasons, the service wants to mask. | None |
| 500 (Internal Server Error) | The general catch-all error when the server-side throws an uncaught exception. | None |
| 503 (Service Unavailable) | The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. | None |
| 504 (Gateway Timeout) | The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. | None |