Errors

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:

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.

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