One workflow, three responsibilities
Your server creates a transaction through the API. The person completes identity verification in the hosted journey using the returned link. Your application reads the result and receives events to continue its business process.
- Create: call
POST /v1/face-auth/transactionswithX-API-Keyfrom your backend. - Hand over: use the returned URL; never send your key to the person’s browser.
- Track: associate
transaction_idwith your process, verify webhooks and reconcile state with GET.
What the result means
Identity verification is one step in your workflow. An approved identity does not automatically approve credit, a purchase, an account or a person’s authority to represent an organization. Your system remains responsible for commercial rules, unresolved cases and the decision to proceed.
status describes the operational stage; decision is pending, approved or rejected. Do not interpret an intermediate step as approval. Expired journeys also require a specific outcome in your application.
Choose a starting point
Use the local simulator to understand the workflow without credentials or personal data. To integrate your backend, follow the quickstart and consult the API reference.
Examples use synthetic data and a reserved documentation address. Your API base URL, credentials and environment access are established during integration enablement.