Welcome to Trulioo's developer portal. This portal hosts documentation for the whole developer lifecycle as outlined below, so that you can refer to it at any stage of your integration with GlobalGateway - GlobalGateway - Trulioo provides a collection of API methods to help you build business processes powered by the GlobalGateway Normalized API. .
Before testing any of Trulioo's APIs or products the most important thing you will need is credentials. Follow the steps in Keys and Authentication to talk to our support team about getting set up.
This portal has been arranged to make the information you need as easy to find as possible. The navigation bar to the left has been divided into Trulioo's main product offerings. Every product section has the following:
Each overview links out to subpages describing common workflows and issues or any other information that developers might need.
The API reference contains full documentation of all the endpoints in Trulioo's API, as well as an interactive web console to make test calls.
The GlobalGateway Normalized API ( NAPI - NAPI - 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. ) is a stateless web service based on RESTful architecture. The production endpoint is supported solely on HTTPS. All requests to the production endpoint need to be SSL/TLS compliant. The base url for the API is https://api.globaldatacompany.com
Request and response body data are required to be in JSON format and can be found here. The output JSON should not be treated as fixed or as a schema. New fields may be added as the API evolves. Clients must not rely on the order in which data appears in JSON service responses and should be resilient to the reordering of fields within a JSON object. The Content-Type header value must be set to "application/json; charset=utf-8".
We use built-in HTTP features, such as HTTP authentication, errors, and verbs which are understood by standard HTTP clients.
For faster response times, include an Accept-Encoding header with a value of "gzip, deflate" and responses will be gzipped.
If this is your first integration with Trulioo you should have access to a demo account, which is your sandbox environment. If you are unsure whether you have a sandbox environment, or how to access it, please contact support.
The sandbox environment is intended to let you get a feel for how Trulioo's API works, but does not perform live transactions against real data. Rather, it checks the given identity against a static test database hosted by Trulioo. For this reason you will need to use a test entity.
A test entity is a dummy identity provided by Trulioo, which matches a record in Trulioo's test database. Test entities can be safely verified in demo accounts without having any impact on real people or data.
There are 2 ways to obtain test entity data. The first is to log into Trulioo's web portal, select "Verify" in the left-hand menu, choose any country, hit the "Populate" button, and copy the test data from the UI. The second is to make an API call to Get Test Entities.
These quick start guides will walk you through the process of your first verification:
If you are unsure which one to pick, you should probably start with identity verification, which is the basic KYC ("Know Your Customer") solution for verifying individuals.
Once you've read the quickstart guides, you can dig deeper with the integration best practices guide. This guide gives an idea of what your integration with Trulioo might look in production and lists Trulioo's recommended best practices for a successful integration.
As you build your integration and get ready for go-live, Trulioo recommends working closely with the support team to ensure you are set up for success. You will receive any assistance you need to guarantee that your integration goes as smoothly as possible.
Once you're satisfied with your initial test of the API, you can contact Trulioo support to receive live API credentials. This will allow you to begin checking identities against live datasources, rather than Trulioo's hardcoded test entities.
The support team will be there every step of the way to organize a go live date and ensure you have a seamless launch.
Your journey with Trulioo doesn't need to stop with one successful integration.
For example, you might want to incorporate Mobile ID or Global AML Watchlist into your application, or learn more about document verification.
At any point, if you're thinking of expanding or updating your integrations, you can refer back to the API Reference. It provides detailed documentation of every endpoint in Trulioo's API, and has an interactive web console so you can make your initial test calls straight from the browser.
For any other questions or requests, contact Trulioo's support team at email@example.com.