Skip to main content
Looking for Age Verification instead? That’s a different, simpler feature — a min/max age restriction applied during a full KYC verification, based on the scanned document’s date of birth. See Age Verification.
Age Estimation checks whether an end user meets a minimum age requirement using a single selfie — no document scan required in the common case. It’s suited for age-gating use cases (e.g. alcohol, gambling, adult content) where you need a fast yes/no decision without putting every user through a full identity verification. When the AI model isn’t confident enough to decide on its own, the session can automatically step up to a document check, which reads an exact date of birth from the ID. Sessions can be created and reviewed from the dashboard, or created programmatically — see API integration. Charges draw on finances allocated to Age Estimation; see Age Estimation Billing.
Results reach your systems through the result webhook. To list past estimations, filter them, or inspect an individual session, sign in to the dashboard — there is no Partner API endpoint for retrieving sessions.

​
How a Session Flows

1

Create

You create a session with the desired settings. You get back a verification link and an expiry time.
2

Capture

You send the end user to the verification link; they complete the selfie on the hosted capture page.
3

Estimate

The AI produces an age estimate:
  • Confident and above the minimum age → Success.
  • Confident and below the minimum age → Underage.
  • Not confident (within the safety margin) → step-up, if enabled:
    • document step-up enabled → a document check is created and the age is read from the ID’s date of birth (see Step-Up Outcomes).
    • document step-up disabled → the session resolves as Uncertain.
4

Result

When the session finishes, iDenfy sends a result notification to your webhook (if set), redirects the user to the matching redirect URL (if configured), and shows the outcome in the dashboard.

​
Step-Up Outcomes

A document step-up ends in one of the following ways. Note that the document’s date of birth is an exact age, so it is compared directly against the minimum age. The safety margin applies only to the fuzzy AI estimate and is not used here.
Fraud-flagged documents are accepted. iDenfy may flag a document session for possible fraudulent activity even when the document itself was read and the face matched. Because the purpose of the step-up is to establish the age, such a session yields a normal Success / Underage result rather than Uncertain. If your own risk policy needs to act on the fraud signal, contact iDenfy — surfacing it in the result notification is planned but not yet available.

​
Statuses and Outcomes

A session has a lifecycle status, and once it finishes, an outcome. The values below are what the API returns; the dashboard shows the same values as labels. Status Outcome

​
API Integration

Create a Session

Create a session from your backend, with the full request schema and error responses.

Result Webhook

Receive the outcome as soon as a session finishes.