Step 1: Test Authentication

Once you have the username and password for your NAPINAPI - Normalized API - a loosely coupled API; fields may be added to our services and responses as the API evolves, and a client must be able to safely ignore fields and data that are not expected. NAPI can help automate your business processes by performing tasks such as Identity Verification, Business Verification, Document Verification and AML Watchlist. account, you can use the Test Authentication endpoint to check that they're working. The only thing you need to provide in this request is an authorization header, at shown below. To generate the "ACCESS_TOKEN" portion of the header, combine your username and password into username:password and run the resulting string through Base64 encryption. Alternatively, you can use a program such as SOAPUI or Postman to construct the authorization header for you.


GET <<endpoint>>/connection/v1/testauthentication
Authorization: Basic ACCESS_TOKEN


Hello JoeNapoli_API_Demo

You should receive a response containing your username, as shown above. The most common reasons for an error response are:

  • The authorization header isn't set properly. It should be a Base64Base64 - Base64 is a group of similar binary-to-text encoding schemes that represent binary data in an ASCII string format by translating it into a radix-64 representation. Trulioo uses it for our ACCESS_TOKEN and encoding our images for document verification. - encrypted Basic AuthenticationBasic Authentication - Basic Authentication uses standard fields in the HTTPS request header to avoid the need for handshakes. The header is "Authorization: Basic ACCESS_TOKEN” Where ACCESS_TOKEN is “username:password". header.
  • The spelling is incorrect.
  • The wrong credentials were used.

Ensure that you are setting the authorization header correctly, using the right username/password without any typos.

Did this page help you?