Verify users
Create wallet verification flows for age gates, identity checks, residency checks, and other policy-based access decisions.
Issue credentials
Define credential templates, map your records into claims, and create OpenID4VCI wallet offers.
Start building
Start with the quickstart hub. Choose identity verification or credential issuance, then open the guide for your stack.Choose what you are building
Identity verification asks a wallet to prove claims. Credential issuance gives a wallet a credential.
Add one server-side integration point
Use your secret key from a server route, server action, worker, or backend service.
Render or return the wallet handoff
Verification flows show a QR code or mobile deep link. Issuance flows return an OpenID4VCI offer URI.
Keys and environments
Authbound uses separate keys for browser and server code.| Key | Example | Where it belongs |
|---|---|---|
| Secret key | sk_test_... | Server only. Used with X-Authbound-Key. |
| Publishable key | pk_test_... | Browser safe. Used to scope status checks. |
| Client token | Returned per verification | Browser safe for a single verification status flow. |
What each call returns
Authbound has two main server flows. Their responses are easy to confuse, so this is the short version:| Call | Returns | Not |
|---|---|---|
verifications.create | A short-lived verification session with wallet payloads in client_action and a clientToken for browser status checks. verification_url is a hosted browser fallback, not the wallet QR/deep-link payload. | A credential. The wallet presents credentials it already holds. |
openId4Vc.issuance.createOffer | A wallet handoff URI (offerUri and offerQrUri) for an OpenID4VCI offer. | The credential itself. The wallet receives the credential only after it redeems the offer. |
openId4Vc.issuance.get(id) for issuance.
Public API
The API URL depends on your key’s mode:| Key | API URL |
|---|---|
Test (sk_test_..., pk_test_...) | https://sandbox.authbound.io |
Live (sk_live_..., pk_live_...) | Your live API URL |
When something goes wrong
See Troubleshooting for the most common errors when wiring up Authbound for the first time, includinginvalid_key_format, credential_definition_not_found, and 409 Conflict on duplicate definitions.