HTTP Status
All QI Tech APIs use the following standardization for HTTP return status codes, in accordance with RFC 7231:
| HTTP Status | Meaning | Description |
|---|---|---|
| 400 | Bad Request | The request sent contains a formatting error. Usually, we return an explanation of the error in the message body. |
| 401 | Unauthorized | There was an authentication problem. Check if the API Key is correct and in the correct header, as per the Authentication section. |
| 403 | Forbidden | The accessed endpoint is for internal use and is not available for this API Key. |
| 404 | Not Found | The requested data was not found using the provided key. This status is also returned when an invalid endpoint is requested. |
| 405 | Method Not Allowed | The HTTP method used is not supported by this endpoint. |
| 406 | Not Acceptable | The data sent in the request body is invalid. In general, this means the data sent is not valid JSON. |
| 409 | Conflict | The request ID corresponds to an ID that has already been processed. This status is returned in the case of duplicate requests sent to the server. |
| 500 | Internal Server Error | We encountered a problem processing this request. When this error occurs, our specialists are automatically notified and begin analysis and resolution immediately. |
| 503 | Service Unavailable | Indicates an infrastructure unavailability, whether planned or unplanned, on our servers. |