Retrieve a completed Jumio KYX transaction's decision data and captured document/selfie images via the Retrieval API v3
domain: documentation.jumio.ai · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine the correct region-specific Retrieval API host (amer-1, emea-1, or apac-1) matching where the transaction was processed
Call GET on the workflow-executions/{workflowExecutionId} resource under your accountId to fetch overall status, credentials, and decision data
For each credential returned, call the credential parts endpoint with the desired classifier (e.g. FRONT, BACK, FACE) to pull the binary image
Persist the decision payload and images into your own case record before any configured retention window elapses
If retention/deletion is required, use the corresponding DELETE endpoint to purge PII/biometric data once you've archived what you need
Known gotchas
This is the KYX v3 Retrieval API — the legacy /v2/scans/{scanReference}/data (Netverify) endpoint belongs to the older product and returns a different shape
Calling the wrong regional host for a transaction processed in another region returns a not-found error, not a redirect
Jumio applies its own data retention policy — images and PII can become unavailable via the API after the configured window even if your own copy still references the workflowExecutionId
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?