--- title: HTTP/Error Codes slug: api/httperror-codes icon: 🚨 docTags: createdAt: 2025-06-10T02:33:03.390Z --- # API Error Handling and Resolution To support smooth integration and effective troubleshooting, this section provides a list of HTTP error codes that may be returned by the Data Zoo KYC Data API. These status codes follow standard HTTP conventions and are intended to help developers quickly identify and address issues during implementation and ongoing use. ## API Responses ### Success | **Success Code** | **Description** | | ----------------- | ----------------------------------------------------------------------------------------------- | | **200 **- OK | Indicates that the request was successfully received, understood, and processed by the server. | ### Error Each code is accompanied by possible causes and suggested resolutions. | **Error Code** | **Description** | **Possible causes** | | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **400 **- Bad Request | Indicates that the server cannot or will not process the request due to something that is perceived to be an error from client side. | ▪️Invalid JSON or malformed request body.
▪️Missing required query parameters or headers.
▪️Invalid values or formats (e.g., wrong data type).
▪️Incorrect content type (e.g., sending text/plain when application/json is expected).

Example,
:::BlockQuote "validationErrors": \[ "Invalid value for dateOfBirth should be: in format YYYY-MM-DD or DD-MM-YYYY." ], ::: | | **401 **- Unauthorized
| The request failed as valid authentication credentials for the target resource. | No credentials were provided, or the credentials provided (e.g. API key, token, username/password) are invalid or expired.

Example,
:::BlockQuote `{ "error": "Incorrect log in credentials detected" }` ::: | | **403 **- Forbidden
| Indicates that the client’s identity may be known, but they do not have permission
to access the requested resource. | ▪️The user is authenticated but lacks required permissions or roles.
▪️The resource is restricted (e.g., admin-only access).
▪️IP address or region has been blocked.
▪️Access is intentionally denied due to policy or configuration. | | **404 **- Not Found | Indicates that the server is reachable, but the specific
URL or resource does not exist or could not be found. | ▪️Incorrect URL or endpoint path.
▪️API version mismatch or deprecated endpoint. | | **405 **- Method Not Allowed | Occurs when a client sends a request where the method is not permitted for the target URL. | Only POST method is allowed. | | **500 **- Internal Server Error | Server failed to process the request due to a problem on the server side | Can be triggered by a wide range of issues. It indicates that something went wrong on the server, but the exact cause is not specified in the response.
| | **503 **- Service Unavailable | Indicates the server is currently unable to handle the request due to temporary overload, maintenance, or downtime. | ▪️Server under high load or experiencing traffic spikes.
▪️Scheduled maintenance.
| | **522 **- Origin Connection Time-out | Indicates the request was aborted due to connection issue. | Common causes of a 522 error include an overloaded origin server, firewall or security settings blocking Cloudflare, long-running processes, or network issues between Cloudflare and the server. | ### Submit a Support Ticket If the issue persists or further assistance is required, [submit a support ticket here](https://datazoo.freshdesk.com/support/tickets/new).