Perform a Trulioo GlobalGateway identity match for a customer in a specified country
domain: developer.trulioo.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Call the get country codes endpoint to confirm the target country is supported and note its two-letter country code
Call the get consents endpoint for that country to retrieve the consent language that must be presented to the user before data is submitted
Construct the verify request body with the country code, a data fields object containing name, address, date of birth, and country-specific national ID fields
POST to the verify endpoint with your API key and the request body
Parse the record results array in the response; each element contains a datasource name and a list of field name match results
Map the overall record status to your internal verification pass or fail logic based on how many required fields matched
Known gotchas
Available data sources and required fields vary significantly by country; test with the test entities endpoint for each target country before going live
Consent language must be shown to the user prior to verification in many jurisdictions; Trulioo may audit for this requirement
Trulioo returns no match and match as field-level results, not a single binary; define your own match threshold policy in advance
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?