The configured customer endpoint that receives a single HTTP POST
from Jumio whenever a workflow execution transitions to a state
Jumio reports out-of-band. The same channel carries every documented
`workflowExecution.status` value; the receiver dispatches on the
`status` field of the payload.
Per the Jumio documentation, the receiver should verify that the
source of the request is one of the pub
Workflow execution has been fully processed by Jumio. The final decision and per-capability results can be retrieved from `workflowExecution.href` via the Retrieval API.
Content-Type: application/json
workflowExecutionAcquisitionStarted
End-user has begun the document / selfie acquisition flow inside the Jumio-hosted UI or SDK.
Content-Type: application/json
workflowExecutionAcquired
All required artifacts have been acquired from the end user. Jumio is now processing them; a `PROCESSED` callback will follow.
Content-Type: application/json
workflowExecutionSessionExpired
The end-user session expired before the workflow could be finalized. The workflow will not be executed further.
Content-Type: application/json
workflowExecutionTokenExpired
The bearer token issued at account creation / update expired before the workflow could be finalized.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.