trulioo.com

Use the username and password for your Trulioo Normalized API account. Trulioo says this account is needed to access NAPI, and if you don't have one you should contact Trulioo Support. Send them as HTTP Basic auth: Authorization: Basic base64(username:password).

To use mTLS, first have a Trulioo normalized API user account and a "Manage mTLS" Customer Portal user account. Generate a private key and CSR, then log in to the Customer Portal with your Manage mTLS credentials, upload the CSR, and download the Trulioo-issued client certificate as described in Connecting to Trulioo's API using Mutual TLS - v1. Install that certificate and its private key on the server making API calls. If you lack either account, contact Trulioo Support.

Obtain a Trulioo Client ID and Client Secret from your Implementation Specialist. The Workflow Studio API docs say these are required for authentication and are not the same credentials as workflow export step credentials. Use them to obtain an access token from http://auth-api.trulioo.com/connect/token as described in Authentication and Workflow Studio (API).

Use your Trulioo KYC Document Verification license key for the Customer API authorization call. The Customer API docs say you pass the license in the authorization header to /authorize to mint transaction access tokens. Trulioo provides a Demo License page in the KYC Docs developer docs, and production credentials are obtained through your Trulioo account/onboarding.

For Customer API v2.5, call /authorize/customer with your license key in the authorization header to receive an accessToken; for v3.0, obtain an OAuth2 client-credentials access token as described in KYC Document API (3.0) and Authentication. Use the returned access token in the Authorization header for subsequent transaction endpoints.