Errors

Search…
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
Code
Description
200 
Everything worked as expected.
204
The resource is deleted.
400
The request has missing arguments or is malformed. See examples of these types of errors.
401
The request is not authenticated.
403
The request is authenticated but does not have sufficient permissions.
404
The resource requested does not exist.
413
The request is too large.
422
A processing error has occurred.
429
The rate limit or service quota has been breached.
500
Something is wrong on our end. Subscribe to our status page to be notified of any incident.
Processing Errors
Error
Description
two_sides_expected
Returned when only one side of a supported document type is provided before running a check.
​
Applies to Document Check.
unsupported_document_format
Returned when an unsupported document attachment format is provided before running a check.
​
Applies to Document Check.
unsupported_document_type_country
Returned when a check is run against an unsupported ID type and country combination.
 
Applies to Document Check.
document_requires_issuing_country
Returned when a check is run against a document with a missing issuingCountry attribute.
​
Applies to Document Check.
document_type_undetected
Returned when an unsupported document type is checked. It could also be returned when the image quality is inadequate to recognize the document.
​
Applies to Document Check and eligible Document uploads.
image_unreadable
Returned when ComplyCube is not able to read data from a document image. This may occur when the image is of low quality or is incorrectly oriented.
​
Applies to Document Check and eligible Document uploads.
under_exposure
Returned when the uploaded document image is too dark. This may occur when the image is underexposed.
​
Applies to eligible Document uploads.
excessive_glare
Returned when the uploaded document image has excessive glare.
​
Applies to eligible Document uploads.
invalid_image_format
Returned when an invalid image format is provided.

Applies to Live Photo, Identity Check, and Document Check.
liveness_failed
Returned when a live photo is deemed likely as spoofed, i.e., not live. It could also be returned when the image quality is inadequate to establish the liveness.
​
Applies to Live Photo.
multiple_faces_detected
Returned when multiple faces are detected. The client must retake the live photo.
​
Applies to Live Photo.
no_face_detected
Returned when no faces are detected. The client must retake the live photo.
​
Applies to Live Photo.
facial_features_obstructed
Returned when facial features are obstructed. The client must retake the live photo.
​
Applies to Live Photo.
face_too_small
Returned when the face is too small. The client must come closer and retake the live photo.
​
Applies to Live Photo.
face_too_close
Returned when the face is too close. The client must move away from the camera and retake the live photo.
​
Applies to Live Photo.
face_not_centered
Returned when the face is too close to the edge of the photo. The client must center their face and retake the live photo.
​
Applies to Live Photo.
face_cropped
Returned when the face has been cropped. The client must retake the photo with their entire face in the frame.
​
Applies to Live Photo.
unsupported_poa_document_type
Returned when a check is run against an unsupported proof of address document.
 
Applies to Proof of Address Check.
unsupported_country
Returned when a check is run against an unsupported country.
 
Applies to Multi-Bureau Check.
Example of Standard Errors
Below, you will find some example error responses from the ComplyCube API.
Forbidden
You'll most likely receive a 401: Unauthorized response when you provide an invalid API key.
1
{
2
    "type": "unauthorized",
3
    "message": "The 'Authorization' header is invalid"
4
}
Copied!
Bad Request
You'll get a 400: Bad Request when you fail validation.
1
{
2
    "type": "invalid_request",
3
    "message": "'personDetails' must be provided when client type is `person`",
4
    "param": "personDetails"
5
}
Copied!
Not Found
When a resource is not found, you will get a 404: Not Found response.
1
{
2
    "type": "resource_not_found",
3
    "message": "Invalid client id '123456789'"
4
}
Copied!
Rate Limited
You will receive a 429: Too Many Requests response when you make too many requests.
1
{
2
  "type": "rate_limit_exceeded",
3
  "message": "You have exceeded the rate limit prescribed to your plan"
4
}
Copied!
Internal Server Error
You'll receive a 500: Internal Server Error response when something goes wrong on our side.
1
{
2
  "type": "internal_server_error",
3
  "message": "An error has occurred, try your request again. If you still keep getting this error, please get in touch with Support."
4
}
Copied!
Service Quota
Pagination
Last modified 6mo ago
Copy link
Contents
HTTP Response Codes
Processing Errors
Example of Standard Errors