Ensure a workflow exists in Onfido Studio and note its workflow ID
POST to the workflow runs endpoint with the applicant ID and workflow ID to create a workflow run and receive a workflow run token
Initialize the Onfido Web SDK or mobile SDK with the workflow run token rather than a legacy SDK token
Register a webhook endpoint in the Onfido dashboard scoped to the workflow run completed event type
On receipt of the webhook, verify the signature using the raw request body and your webhook secret, then extract the workflow run ID from the payload
GET the workflow run resource by ID to retrieve the output field containing the final decision and any reason codes
Known gotchas
Workflow run tokens are single-use and short-lived; do not cache or reuse them across sessions
Webhook payloads must be verified against the X-SHA2-Signature header before trusting any data in the body
The workflow output schema varies by workflow definition; validate the output structure against your specific workflow configuration rather than assuming a fixed shape
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