Skip to main content

API keys

Create keys in the DashboardAPI Keys (verified business accounts only). Each key gives you two secrets, shown once at creation:

API key

anonage_sk_… — identifies your account on the verification endpoints. Send it as the X-API-Key header.

Signing secret

whsec_… — used to verify the HMAC signature on callbacks. See Callbacks.
We store only a hash of your API key, so it can’t be recovered — if you lose it, revoke and create a new one.

Using your key

The API key is a server-side secret. Never ship it to the browser or a mobile app, and never put it in a QR code — open sessions from your backend and hand the browser only the opaque session_id + nonce.

Account vs key auth

Test and live keys

Every key belongs to one environment, and says so in its own prefix: Test keys need a verified email address. Live keys additionally require a verified identity on the account — your Dashboard walks you through both.

Rotating & revoking

Revoke a key in your Dashboard at any time — sites using it stop verifying immediately. To rotate with zero downtime, create the new key, deploy it, then revoke the old one.
Roadmap: per-key allowed origins, and signing-secret rotation with a grace window.