Errors

Learn about our response and error codes.

ComplyCube uses standard HTTP response codes to indicate the success or failure of an API request.

Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided. Codes in the 5xx range indicate an error with ComplyCube's servers.

Some 4xx errors include an error code that briefly explains why the error occurred.

HTTP response codes

Processing Errors

Example of Standard Errors

Below, you will find some example error responses from the ComplyCube API.

Unauthorized

You'll most likely receive a 401: Unauthorized response when you provide an invalid API key.

{
    "type": "unauthorized",
    "message": "The 'Authorization' header is invalid"
}

Forbidden

You'll most likely receive a 403: Forbidden response when you do not have access to the requested resource.

{
    "type": "unauthorized",
    "message": "Your current plan does not include access to this service"
}

Bad Request

You'll get a 400: Bad Request when you fail validation.

{
    "type": "invalid_request",
    "message": "'personDetails' must be provided when client type is `person`",
    "param": "personDetails"
}

Not Found

When a resource is not found, you will get a 404: Not Found response.

{
    "type": "resource_not_found",
    "message": "Invalid client id '123456789'"
}

Rate Limited

You will receive a 429: Too Many Requests response when you make too many requests.

{
  "type": "rate_limit_exceeded",
  "message": "You have exceeded the rate limit prescribed to your plan"
}

Internal Server Error

You'll receive a 500: Internal Server Error response when something goes wrong on our side.

{
  "type": "internal_server_error",
  "message": "An error has occurred, try your request again. If you still keep getting this error, please get in touch with Support."
}

Last updated