HTTP Status
All QI Tech APIs use the following standardization for HTTP return statuses, complying with RFC 7231:
| HTTP Status | Meaning | Description |
|---|---|---|
| 400 | Bad Request | The sent request contains a formatting error. In most cases, 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, 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 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 request ID corresponds to an ID already processed. This status is returned in the case of duplicate requests sent to the server. |
| 500 | Internal Server Error | We had a problem processing this request; when this error is encountered, our specialists are automatically notified and start to work on a solution immediately. |
| 503 | Service Unavailable | You have encountered an unavailability, whether planned or unplanned, of our server infrastructure. |