Error Handling
Our API uses standard HTTP response codes to indicate the success or failure of a request. In addition to these codes, specific errors related to individual endpoints are documented separately on their respective pages. This general guide covers common HTTP status codes and error-handling best practices.
HTTP Status Codes
The following HTTP status codes are commonly used across our API:
| Status Code | Description |
|---|---|
200 OK | The request was successful. |
400 Bad Request | The request was invalid or cannot be processed. |
401 Unauthorized | Authentication failed or the user does not have permissions. |
404 Not Found | The requested resource could not be found. |
429 Too Many Requests | The user has sent too many requests in a given amount of time. |
500 Internal Server Error | An error occurred on the server. |
504 Gateway Timeout | The service is taking longer to respond. |
Verifiet Team will be alarmed and notified in the event of any errors occuring and will investigate further to resolve the issue.