Age verification API

An age verification API your OIDC library already speaks

Redirect the user, get a code back, read age_verified. AgeWallet runs the selfie and ID checks and applies the law for each user’s location. You never handle a document or a date of birth.

  • Standard OpenID Connect
  • PKCE, state and nonce
  • Official SDKs for web and mobile

Four steps, three of them ordinary OIDC

If you have built “Sign in with” anything before, you already know this flow.

  1. Send the user to authorize

    Redirect to /user/authorize with your client ID, redirect URI, PKCE challenge and state.

  2. They verify with AgeWallet

    Face estimation with 3D liveness, or a government ID check, chosen by location and industry rules.

  3. Exchange the code

    Your server swaps the one-time code for tokens at /user/token.

  4. Read the result

    Call /user/userinfo with the access token and grant access only on age_verified: true.

The whole result, in four fields

The response tells you whether the user passed, and nothing you would then have to protect.

Full reference: Verify user age via UserInfo and Endpoints.

# Discovery: point your OIDC library here
https://app.agewallet.io/.well-known/openid-configuration

# After the code exchange
curl https://app.agewallet.io/user/userinfo \
  -H "Authorization: Bearer $ACCESS_TOKEN"

{
  "sub": 89,
  "age_verified": true,
  "expires_at": 1765035995,
  "metadata": "order:XYZ-42"
}

Official SDKs, or bring your own library

The SDKs handle PKCE, state and nonce validation and the token exchange. See SDKs & libraries.

JavaScript (drop-in)

Add a script tag, no build step.

JavaScript SDK

Custom web flows.

PHP SDK & single-file client

No Composer required for the simple version.

iOS & Android

Native Swift, Kotlin and Java.

Flutter, React Native & Ionic

Cross-platform mobile.

Any OIDC library

Point it at our discovery document.

On WordPress, Shopify or Telegram, skip the code entirely: use the WordPress plugin, the Shopify app or the Telegram bot.

Built for production

Compliance in the platform, not your code

Age limits and allowed methods per country and US state come from the Legal Matrix. When a law changes, your integration doesn’t.

Match results to your records

Bind each flow with state, and pass an opaque metadata value such as an order reference that comes back in the result.

Short-lived tokens

Access tokens expire after 900 seconds. Read the result once, store your own decision, and nothing sensitive lingers.

Public clients for mobile

Mobile SDKs use PKCE without a client secret, so no credential ships inside your app.

Simple API pricing

No sales call to find out what it costs. Compare age verification providers.

  • $0.30 per completed verification, the same for face estimation and ID checks.
  • $0.008 per user authorization, logged as your audit trail.
  • No setup fee, no monthly minimum. Abandoned verifications are never charged.
  • $5 of credit on every new account to build and test your integration. See pricing.

Age verification API questions

What kind of API is the AgeWallet age verification API?

It is a standard OpenID Connect authorization code flow. You redirect the user to AgeWallet, they verify their age, AgeWallet sends them back with a one-time code, and your server exchanges the code for tokens and calls /userinfo to read the result.

What does the API return?

The /userinfo endpoint returns age_verified (true or false), a stable user identifier (sub), an expiry timestamp (expires_at), and any metadata string you sent with the request. It never returns a date of birth, name or document.

Do I need an SDK?

No. Any OAuth 2.0 or OIDC library that supports discovery can connect using https://app.agewallet.io/.well-known/openid-configuration. Official SDKs for JavaScript, PHP, WordPress, iOS, Android, Flutter, React Native and Ionic handle PKCE, state and nonce for you.

Can I use it in a mobile app?

Yes. The iOS, Android, Flutter, React Native and Ionic SDKs run as public clients with PKCE, so no client secret is stored in the app.

How do I match a verification to an order or user in my system?

Bind the flow to your own user or session with the state parameter, and optionally attach an opaque metadata string, such as an order reference, on the authorization request. AgeWallet returns it unchanged in the /userinfo response.

How much does the API cost?

$0.30 per completed verification and $0.008 per user authorization, with no setup fee or monthly minimum. API access and the SDKs are included, and new accounts start with $5 of credit to build and test.

Which verification methods does the API trigger?

AgeWallet chooses the method for each user from their location and your industry settings: facial age estimation with 3D liveness, falling back to a government ID check when needed, or ID straight away where the law requires it. Your integration code stays the same either way.

Get your client ID and ship it this afternoon

Register, create a client, and point your OIDC library at our discovery document. Your first $5 of verifications are on us. Want the bigger picture first? Read about the AgeWallet age verification service.