Get verification status (client-side)
Lightweight endpoint for polling verification status from client-side code. Uses the verification-scoped client token and publishable key instead of a secret key.
Returns minimal data suitable for client display.
Enabled isolated testbed: this session’s unexpired Bearer client_token is sufficient; the publishable key may be omitted.
Authorizations
Opaque verification-scoped client token. Returned when creating a verification. Treat it as a bearer secret and do not depend on its internal format.
Browser-safe publishable key. Format: pk_live_* (production) or pk_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 status
Lightweight status for client-side polling
verification_status created, awaiting_user, awaiting_provider, processing, verified, failed, canceled, expired presentation_invalid, credential_expired, credential_revoked, issuer_untrusted, policy_not_satisfied, processing_timeout, provider_error, user_declined, wallet_error, null Present only while the verification can still be handed to a wallet. Terminal statuses never include wallet handoff data.
Where the hosted verification page sends the user once the verification finishes, as given on create.
2048