HTTP Status
All QI Tech APIs use the following standardization for HTTP response status codes, in accordance with RFC 7231:
| HTTP Status | Meaning | Description |
|---|---|---|
| 400 | Bad Request | The request sent contains a formatting error. In most cases, we return an explanation in the response body indicating where the error is. |
| 401 | Unauthorized | There was an authentication issue. Please verify that the API Key is correct and sent in the proper header, according to 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 does not apply to the accessed endpoint. |
| 406 | Not Acceptable | The data sent in the request body is invalid. In general, this means the payload is not a 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 an issue while processing this request. When this error occurs, our specialists are automatically notified and immediately begin analysis and resolution. |
| 503 | Service Unavailable | You have encountered a planned or unplanned infrastructure outage of our servers. |