HTTP Status
All QI Tech APIs use the following standardization in HTTP return statuses, according to RFC 7231:
| HTTP Status | Meaning | Description |
|---|---|---|
| 400 | Bad Request | The request sent has some formatting error. In most cases, we return in the message body an explanation of where the error is. |
| 401 | Unauthorized | There was a problem with authentication, 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 key used. 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 that the data sent is not valid JSON. |
| 409 | Conflict | The request id corresponds to an id already processed previously. This status is returned in case of duplicate requests sent to the server. |
| 500 | Internal Server Error | We had a problem processing this request, when we encounter this error our specialists are automatically notified and start analysis and resolution immediately. |
| 503 | Service Unavailable | You encountered a planned or unplanned unavailability of our server infrastructure. |