Create a workflow in Entrust Workflow Studio (formerly Onfido Studio) that chains a Document Capture task to a Facial Similarity task; note the workflow_id for API calls.
Generate a short-lived SDK token by calling the Entrust Identity Verification API with your API token (Authorization: Token token=YOUR_TOKEN) and specifying the applicant_id and the workflow_id.
Initialize the Entrust Web or Mobile SDK with the sdk_token to present the capture interface to the user; the SDK handles document type guidance and image quality checks.
On SDK completion, call GET /v3.6/workflow_runs/{workflow_run_id} to retrieve the workflow result including document data extraction and biometric match output.
Consume the decision payload — approved, declined, or review — and the sub-results for each task to populate your onboarding decision.
Configure webhook delivery in the Entrust dashboard to receive workflow.finished events for asynchronous processing; verify the X-SHA2-Signature header on incoming payloads.
Known gotchas
Onfido was acquired by Entrust; the documentation domain is now documentation.identity.entrust.com and SDK package names changed; legacy package references will fail in new builds.
SDK token validity is short (typically one hour); if the user session exceeds this window, a new token must be generated and the SDK re-initialized rather than reusing the expired token.
Applicants are immutable once created; always create a new applicant object per verification session to avoid cross-contaminating biometric and document data between distinct users.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp