Skip to main content
This page uses the original routes, which keep working. For new integrations, see Age Verification. For when and how to use Age Verification in a trust-and-safety or KYC flow, see the Age Verification guide.

Endpoint

Request

POST /verify-age takes one field. lead_info and input are aliases for subject. Other keys, including struct, tier and webhook_url, are ignored; poll for the result. The response is the job handle:

Status

GET /verify-age/{task_id} returns {"task_id", "status"} until the job finishes, and the full result once status is completed.

Response

Each date component is null unless a source establishes it, and day and month are always null when year is. age.value can be set while the date components are null.

Usage

Pricing

See Credit Costs for more information. Age Verification needs no tier access: any organization with credits can call it.