Verify a user's identity with the Trulioo identity verification API
domain: developer.trulioo.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate using your Trulioo API key passed as the x-trulioo-api-key header (or via Basic Auth depending on the API version your contract uses).
Call the getCountryCodes endpoint and then the getFields endpoint for the target country to discover which data fields are required or optional for that jurisdiction.
Submit a verification request to the verify endpoint with the DataFields object populated with the user's personal information (name, date of birth, address, national ID number where applicable) and specify the CountryCode.
Parse the synchronous response: check the Record.RecordStatus field for 'match', 'nomatch', or 'missing' and inspect the DatasourceResults array for per-source results and field-level match details.
Handle 'nomatch' outcomes by reviewing which datasources returned mismatches and deciding whether to prompt the user for data correction or route to manual review.
Log the TransactionID from the response for audit trail purposes; use it to retrieve the transaction later if needed.
Known gotchas
Field requirements vary significantly by country; always call getFields dynamically for the user's country rather than hardcoding a field set.
Trulioo has transitioned to a newer platform (GlobalGateway 4 / Trulioo Identity Verification); confirm which API version your account is provisioned on before coding.
Trulioo verification is generally synchronous for most countries but can behave differently for certain document or biometric add-ons; check product documentation for your specific package.
Give your agent this knowledge — and 15,500+ 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?