Obtain your Jumio API token and secret for the target datacenter region and base64-encode them for Basic authentication
POST to the account creation or account update endpoint to register the end user and receive an account ID
POST to the workflow execution endpoint with the account ID and the desired workflow definition ID for document verification
Return the web URL or SDK token from the response to the client to initiate the document capture session
Configure your callback URL in the Jumio portal; when the transaction completes Jumio POSTs the decision payload to your endpoint
Parse the callback payload for the overall decision field and the document extraction fields such as extracted first name, last name, date of birth, and document number
Known gotchas
Jumio operates separate API base URLs per datacenter region (US, EU, SGP); using the wrong base URL returns authentication errors even with valid credentials
Callback payloads can arrive multiple times for a single transaction as processing stages complete; implement idempotent handling keyed on the transaction reference
Some workflow definitions require specific document types to be explicitly allowed in the portal configuration before they will be accepted
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