Skip to main content
Requirements:
  • API key pair (API key + secret)
  • Age Estimation feature enabled on your contract (contact iDenfy to activate)
  • Finances available for Age Estimation
For how the feature works, what each outcome means, and how billing works, see the Age Estimation Overview guide. This documentation focuses on the API integration.

Create a Session

Authenticate with your API key pair — API key as the username, API secret as the password, over HTTP Basic. Sessions are scoped to your partner account, so you only ever see your own.
For the full request and response schemas, every field’s constraints and defaults, and an interactive playground, see the API Reference page for this endpoint.
Creating a session pre-checks your Age Estimation finances; if they can’t cover the session the request is rejected — see Errors.

Example (Partner API)


Errors

The response body identifies which finances are short:
When handling this response:
  • Read missing_pool_funds to identify which finances are short. The response uses fund_pool naming for what the guides call Age Estimation finances.
  • missing_funds stays null — it covers general funds only, so do not read it to detect exhausted Age Estimation finances.
  • missing is the shortfall in your account currency, and 0 when no Age Estimation finances are configured.
Insufficient funds return 402, not 403. This matches iDenfy’s other token-creation endpoints — see ID Error Messages. 403 is reserved for an account that lacks access to the endpoint or feature.

What’s Next

Once you have a session_url, send the end user to it to complete the selfie capture. When the session finishes, the result is delivered via the result webhook — this is the only way to receive it programmatically, so configure one. Past sessions can be listed and inspected by signing in to the dashboard; see Session List.