Skip to main content

​
Development environment

Integrate against the development base URL while you build:
It behaves exactly like production but is backed by a sandbox identity provider, so you can run the whole loop — open a session, present with a test wallet, receive a signed callback — without real KYC.

​
A good end-to-end test

1

Open a session

Call POST /api/age-verification/session from your server and render the QR / tap-link.
2

Present with a verified test wallet

Approve in an AnonAge wallet that has completed sandbox verification, so the session resolves.
3

Assert your callback ran

Confirm your callback_url received a request, the signature verified, and you recorded the result. Then confirm polling GET /api/age-verification/session/{id} agrees.
4

Test the unhappy paths

A forged/unsigned callback must be rejected (401 on your side); an expired session must not resolve; a second present on the same session must be ignored.
Roadmap: dedicated test and live API keys. A test key will run against sandbox and never bill, so you can keep an integration test suite running against your live account safely.

​
Going live

  1. Point your base URL at https://api.anonage.io.
  2. Swap your development key for a production key from the Console.
  3. Make sure your callback_url is publicly reachable over https and verifies signatures.