Age Estimation Webhooks

When a session reaches a terminal state, a result notification is sent to your endpoint.

Where It’s Sent

iDenfy resolves the destination in this order:

The token’s webhook_url, if set (per-session override).
Otherwise, the webhook URL configured on your account’s Age Estimation notification (notification event type AGE_ESTIMATION) — this is the default used when a token has no webhook_url.
If neither is configured, no notification is sent — the result is still available via the API.

If your Age Estimation notification is configured with a signing key, the webhook body is signed so you can verify authenticity. See Callback Signing.

Payload

The API Reference page for this webhook isn’t published yet. Once Age Estimation is released, it will appear there automatically with the full schema — no further changes needed on this page.

Field	Type	Description
`scanRef`	string	The step-up scan reference, or the token id when there is no scan ref.
`status`	enum	`COMPLETED` or `FAILED`.
`outcome`	enum \| null	See Enumerations.
`verdict`	string \| null	Model verdict (e.g. `ADULT`).
`estimatedAge`	integer \| null	The established age. When a document step-up produced an age, that exact document age is reported; otherwise it is the AI face-estimated age.
`confidence`	float \| null	Model confidence.
`clientId`	string \| null	The `client_id` supplied at creation.
`occurredAt`	datetime	When the terminal event occurred.

The notification does not distinguish a document that was accepted cleanly from one that was accepted but flagged for possible fraud — both report the same outcome.

Idempotency

Delivery may be retried, so handle notifications idempotently (e.g. keyed on scanRef / clientId).

Start Here

ID Verification (KYC)

Business Verification (KYB)

AML Screening

Face Authentication

Age Estimation

Fraud Prevention

Bank Verification

Going Live

Reference

Where It’s Sent

Payload

Idempotency

​Where It’s Sent

​Payload

​Idempotency

Where It’s Sent

Payload

Idempotency