Standard API errors
When interacting with iDenfy API you may encounter error responses. This means that you have tried to do an action which is not allowed or malformed in some way.
A standard error response has a HTTP status code 400 and a JSON body which contains:
| JSON key | Explanation |
|---|---|
identifier | A constant indicating a type of error. Never changes, therefore can be used in code to automate processes. For possible values see the table below. |
message | A human readable message describing an error. Mainly used for programers to get a clue of what went wrong. |
Error identifier constants
A list of error constants and their explanations.
| Error identifier | Explanation |
|---|---|
INTERNAL_ERROR | Unhandled unknown internal error at iDenfy's API side. |
BAD_VALUE | Supplied value is not valid. |
MISSING_VALUE | Expected a supplied value but got none. |
UNAUTHORIZED | Missing API key/secret in HTTP headers or API key/secret not valid. |
ENCODING_ERROR | Failed to encode/decode object. |
JSON_ERROR | Malformed JSON body. |
TOKEN_NOT_VALID | Verification token is not valid or expired. |
PARTNER_CONTRACT_ERROR | A partner can not do a requested action because of the signed contract. |
METHOD_NOT_ALLOWED | Wrong HTTP method. |
PERMISSIONS_ERROR | Insufficient permissions for the request. |
TOO_MANY_REQUESTS | Requests per hour limit has been reached. Default value is 10000. |
VALIDATION_ERROR | Request is malformed. |
important
A common error that results in 400 Bad Request with a message "Partner reached token limit." And identifier "PERMISSIONS_ERROR" when trying to generate a token means that your environment has run out of verification tokens. Please contact our support team in a Dashboard using your account.