See Errors for a full description of each of the errors listed below.

Http Errors

The API uses HTTP response codes to indicate the status of a request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate that a failure occurred due to the content or structure of the request (e.g., a required parameter was omitted, the authentication header is missing, etc.), and codes in the 5xx range indicate a server error. 5xx errors are rare, and should be handled by emailing Trulioo support. Here are some troubleshooting tips for the more common 4xx errors:

400 BadRequest

Details should be included in the body of the response. Some example causes of a 400 BadRequest are:

Message

Troubleshooting

Account not configured for this product

Ensure you are configured properly with the Get Country Codes request to see the countries you are configured for.

Configuration name not valid

For now, you should always send "Identity Verification" for the configuration name parameter.

Unable to find account

Email Trulioo support to ensure there are no issues with your account.

Transaction not available

Make sure that you are sending the correct TransactionRecordID and that the verify was sent from this same request.

Account not configured for this country.

Try the Get Country Codes request to see the countries you are configured for.

401 Unauthorized

The user name and password you provided is not valid or you are using an account that does not have API permissions. Make a call to Test Authentication with your username/password in the Authentication header. If you do not see your username echoed back at you, you are using the incorrect password or account.

Missing authorization header

If you are using one of our generated code samples and are receiving the response "Missing authorization header" see Authorization Headers to get examples of how to add them to each language.

413 Request Entity Too Large

If the request you sent is over the current limit.

415 UnsupportedMediaType

You asked for a media type that we do not support. Make sure your request includes a Content-Type: application/json header.

Service Errors

Service errors are caused by invalid customer data, datasource errors, and address correction/address validation issues. Each error includes a code, indicating the category of service error, and a detailed error message.

Code

Message

1000

Provider Error - There was an error connecting to the source

1001

Missing Required Field

1002

Datasource Unavailable - the source did not respond

1003

Datasource Error - The source returned an error

1004

State not supported (AU Driver license)

1005

Missing consent - consent not sent for the source

1006

Unrecognized Field Name

1008

Invalid Field Format

1009

Unrecognized Field group

1010

Request Timed Out

1011

Duplicate Field received

2000

Unrecognized Error

3000

Address Corrected

3001

State Province Changed

3002

City Changed

3003

Street Info Changed

3004

Postal Code Changed

3005

Missing Address Info

3008

Cannot validate address

3009

Address validation is not available

4001

Missing Required Field: MobileNumber

4002

Invalid Mobile Number

4003

Mobile Carrier Not Supported

See the Verify documentation for JSON examples of how errors are returned.