Create or update an account via POST to the Jumio REST API with your Basic Auth credentials (API token and secret) and the desired workflow ID (e.g., workflow 200 for ID + Identity).
Retrieve the web or SDK initialization URL from the account creation response and direct the user to it for document capture and selfie submission.
Configure a callback URL in the Jumio Customer Portal; Jumio will POST a callback payload to this URL after processing completes, containing the account ID, workflow run ID, and decision.
Use the workflow run ID from the callback to call GET /api/v1/accounts/{accountId}/workflow-executions/{workflowExecutionId} to retrieve the full verification result including extracted data fields and rejection reasons.
Map Jumio decision values — PASSED, FAILED, WARNING — along with sub-decision codes to your onboarding acceptance logic.
Test in the Jumio sandbox using provided test credentials and trigger simulated outcomes before connecting to the production environment.
Known gotchas
Jumio's API credentials are region-specific (US, EU, SGP); using a credential from the wrong region against the wrong base URL will return authentication errors rather than a meaningful region mismatch message.
The callback payload must be validated by comparing the transaction reference against your own records before acting on any decision, as the callback endpoint is unauthenticated by default unless you configure callback verification.
Workflow IDs encode the specific verification steps performed; selecting the wrong workflow ID results in missing biometric comparison or liveness checks that your compliance policy requires.
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