Create a verification
Creates a new identity verification. Returns a verification-scoped client token and wallet handoff action data for QR, link, or request-blob flows.
The verification will expire after the configured TTL (default 15 minutes).
Enabled isolated testbed: omit all API credential headers to create without a key. Anonymous retries ignore Idempotency-Key. Both creation routes share 20/minute and 300/hour across testers. The enabled testbed caps raw bodies at 256 KiB before authentication, even for supplied keys (413). Customer-controlled edge deployments require a secret-key header and cap creation bodies at 64 KiB after validating the header format (413). Credential authorization happens downstream of envelope validation; this limit and validation order are separate from the enabled isolated testbed.
Authorizations
Server-side secret key header. Format: sk_live_* (production) or sk_test_* (testing).
Headers
Unique key for idempotent requests
255Body
Policy to use for this verification
100^pol_[a-z0-9_]+_v\d+$"pol_age_over_18_authbound_v1"
Override provider selection
auto, eudi Provider-specific protocol options for the selected verifier. Omit them to use the policy profile's options: HAIP policies hand off with direct_post.jwt, profile haip, JAR by reference and a GET request URI, and AVP policies with plain direct_post. When given, eudi must name exactly that profile's set, optionally with the policy's authorization_request_scheme; any other set is a validation_error on provider_options.
Your reference for the end user
255Custom metadata (stored, returned in responses)
Absolute http(s) URL, without userinfo or fragment, on an origin registered for the project (or localhost with a test key; a live key needs https and a public host) that the hosted verification page returns the user to.
2048Response
Verification created successfully
Unique identifier
"vrf_abc123"
verification test, live created, awaiting_user, awaiting_provider, processing, verified, failed, canceled, expired "pol_age_over_18_authbound_v1"
Opaque verification-scoped client token. Returned when creating a verification. Treat it as a bearer secret and do not depend on its internal format.
"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9..."
SHA-256 hash of policy at creation time
Selected provider ID
eudi "eudi"
Reason for failure (only when status=failed)
presentation_invalid, credential_expired, credential_revoked, issuer_untrusted, policy_not_satisfied, processing_timeout, provider_error, user_declined, wallet_error, null Action data for user to complete verification
Link to the hosted verification page, returned on create when the installation has one, while the verification can still be handed to a wallet and its response mode is not dc_api.jwt. Its fragment carries the client token and the publishable key, so it is a bearer link. Redirect the user's browser to it; never show it as a QR code or write it to a log. For the wallet handoff, use client_action.data.
Your reference for the end user
Custom metadata
When verification reached terminal state
The return_url given on create, which the hosted verification page returns the user to.
2048