HTTP Status
All QI Tech APIs use the following standardization for HTTP response status codes, in accordance with RFC 7231:
| Status HTTP | Meaning | Description |
|---|---|---|
| 400 | Bad Request | The request sent has a formatting error. In most cases, we return an explanation in the response body indicating where the error is. In this API we implement a set of specific error codes to help you understand what may be wrong. |
| 401 | Unauthorized | There was an authentication problem; verify that the API Key is correct and in the correct header, as described in the Authentication section. |
| 403 | Forbidden | The endpoint accessed is for internal use and is not available for this API Key. |
| 404 | Not Found | The requested data was not found using the key provided. This status is also returned when an invalid endpoint is requested. |
| 405 | Method Not Allowed | The HTTP method used (POST, GET, PUT, ...) does not apply to the endpoint used. |
| 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 document id sent matches an id that was already processed previously. This status is returned in the case of duplicate requests sent to the server, or requests for two documents with the same id. |
| 500 | Internal Server Error | We had a problem processing this request. When this error occurs our team is automatically notified and begins analysis and resolution immediately. |
| 503 | Service Unavailable | You have encountered an outage, planned or not, of our server infrastructure. |