Retrieve a verification
Retrieves the verification object including current status, policy information, and timing details. Secret-key requests include merchant management fields such as customer_user_ref and metadata. Client-token requests are intended for embedded browser flows and return only browser-safe verification fields.
Enabled isolated testbed: this session’s unexpired Bearer client_token is sufficient; the publishable key may be omitted.
Authorizations
Server-side secret key header. Format: sk_live_* (production) or sk_test_* (testing).
Path Parameters
Verification ID. Runtime IDs may be UUIDs during alpha; external IDs use vrf_*.
^(vrf_[a-zA-Z0-9_-]+|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-5][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12})$Response
Verification details
Unique identifier
"vrf_abc123"
verification test, live created, awaiting_user, awaiting_provider, processing, verified, failed, canceled, expired "pol_age_over_18_authbound_v1"
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