Some troubleshooting codes (table)

1001

Query ID must be between 20 and 40 symbols.

1002

Query ID must be a valid UUID V4

1003

Query ID must be unique, it has already been used.

1102

Mandatory parameters are missing from the request.

1104

Request includes invalid parameters.

1201

Invalid timestamp. Timestamp must not be older than one hour.

1202

Timestamp format is incorrect. YYYY-MM-DDTHH:MM:S+Timezone Offset|Z or UTC.

1203

Invalid ISO 8601 date. Date needs to be in format YYYY-MM-DD.

1301

Requested features are not supported.

1302

Only HTTPS return URLs are allowed.

1303

Invalid status.

1304

Cannot transition to "$STATUS" status.

1308

ID number is missing.

1309

SSN validation requires person firstName + lastName OR fullName to be provided.

1310

SSN validation requires person.dateOfBirth or address data to be provided.

1400

Image data not found.

1401

Image is not in valid base64.

1402

Image context is not supported.

1403

Image property is missing.

1500

vendorData field cannot be more than 1000 symbols. We require only non-semantic data to be submitted (UUID-s etc., that can not be resolved or used outside the customer's domain)

1501

vendorData must be a string. We require only non-semantic data to be submitted (UUID-s etc., that can not be resolved or used outside the customer's domain)

1804

Integration with API key is not active. This error occurs when your integration has been deactivated. This can happen due to account suspension, billing issues, or manual deactivation. Contact Veriff support to reactivate your integration or verify your account status.

1815

Could not authenticate request. This error occurs when the system cannot validate the request signature or authentication headers. Check that the headers to not have typos and includes correct values. Check that you use the correct and full request body to create the signature.

1818

Signature does not match the hmac-sha256 of query id and integration api secret. This error occurs when making API calls to retrieve session data. Unlike session creation requests, data retrieval endpoints require a different signature calculation method. Ensure you're generating the HMAC signature using the correct parameters for the specific endpoint you are calling (see the endpoint’s documentation for info), and using your integration's shared secret key (not the public API key)

1819

Signature does not match the hmac-sha256. This error indicates that while the request format is correct, the HMAC-SHA256 signature computed by Veriff does not match the signature provided in your X-HMAC-SIGNATURE header. Ensure you are using your integration's shared secret key (not the public API key) and the exact raw request body when generating the signature.

2003

Date of birth is not a valid date.

2101

Document number has to be between 6 and 9 characters.

2102

Document number may contain only characters and numbers A-Z, 0-9.

2103

Document type is not supported.

2104

Document from provided country is not supported.

Aug 14, 2025

Error codes added: 1804, 1815, 1818, 1819

Mar 12, 2025

Documentation published