Title
Create new category
Edit page index title
Edit category
Edit link
Create a session
The integration steps are as follows:
Create a session
Launch the user view
Retrieve results
First, you will need to create a session. This is done by making a POST request to the sessions endpoint.
Header | Description |
|---|---|
Authorization | API Key to call the Yoti Age API. Should be sent as a |
Content-Type | application/json |
Yoti-SDK-Id | Your unique Yoti-Sdk-Id (UUID), obtained from the Yoti Hub |
The age verification API uses an HTTP authentication scheme called ‘bearer authentication’. This involves security tokens called "bearer tokens". They are the predominant type of access token used with OAuth 2.0. A resource should interpret a bearer token as "Give the bearer of this token access". The client must send this token in the Authorization header when making requests to protected resources.
Your API Key must remain strictly confidential. It must be stored securely. We advise that you never commit any code containing your API Key, and never share it with anyone other than the authorised party.
If you believe your API key has been compromised, please generate new API keys in the Yoti Hub as soon as possible.
Request body
In the request body, you need to provide the methods you would like to enable, the allowed age threshold, and your client preferences. If you have created a template before, you can create a session using a template_id.
Type parameter
This is where you define what preference you want to set for the age of the user.
Parameter | Description |
|---|---|
OVER | If the user is OVER an age threshold (e.g., over 21). |
UNDER | If the user is UNDER an age threshold (e.g., under 30). |
AGE | This will return the estimated AGE of the user (e.g., if the user is estimated to be 25, we will return 25.) |
Note: If the type parameter AGE is used, Yoti will return the detected Age value without comparing against the threshold. It allows the integrator to utilise this value to compare on their side against multiple thresholds.
Configuration parameter
Here are the parameters for the create session object.
Parameter | Type / Value | Description | Templates |
|---|---|---|---|
reference_id | string | (optional) Reference ID is a string. Yoti returns this same string in the session result. Note: We recommend that you do not include any personal information in this string. | ✅ (optional) |
ttl | seconds | (required) The time the session is valid for. The user will need to complete the session before the ttl expires. This must be at least 60 seconds (1 minute). And cannot be longer than 1 month. | ✅ (required) |
callback | object | The URL to redirect your user to after they complete age verification. The Example - Enabling the | ✅ (Only required if not configured in the template) |
callback_url | string | Shorthand for specifying the URL where your user is redirected after age verification. By default, Example - https://www.example.com | ✅ (Only required if not configured in the template) |
notification_url | The URL where the results of an age verification should be sent. This endpoint must use HTTPS and accept POST requests for notifications. | ✅ (Only required if not configured in the template) | |
block_biometric_consent | true/false | In several US states (currently Texas, Illinois, and Washington), the law mandates that you obtain the user’s specific consent to collect their biometric details for our liveness or face-matching feature to be compliant with US legislation. For any other countries or states within countries. If you choose only to request specific consent in the above "territories", you must provide details of the effective geo-location software you use to prevent any individuals located in one of these territories from accessing the Yoti service without prior giving specific consent. Setting to true bypasses this screen. We recommend keeping this value to the default (false) to enable consent for all users. | |
cancel_url | You can specify a cancel URL; if the user opens AVS and decides that they don't want to continue, then they can be taken to a specific place rather than going back in the browser. If you would like to see how this looks, please head over here. | ✅ (Only required if not configured in the template) | |
retry_enabled | true/false | You can give the user the ability to retry verifying their age if an attempt fails. Webhooks are sent for each age verification attempt, so some could show up as "FAIL" even if the user eventually passes. | |
resume_enabled | true/false | This allows the user to resume a session (if the link is re-accessed). The user can be resent the link if, for instance, the doc_scan session fails, so that they can retry. | |
rule_id | string | This allows an age token rule ID to be specified. If a user has previously passed a session and did so by meeting the age threshold configured in your rule, the user will automatically redirect to the callback. You will need to enable Reusable checks for this. The login method must be enabled for this to take effect. | |
synchronous_checks | true/false | If set to true, ensures that all methods have a result ready before the user is redirected to the callback URL. Default is false; this primarily affects document checks and credit card checks, as these are async. | |
retry_limit | integer | The total number of attempts a user is allowed in each method. | |
template_id | string | A template ID (UUID) obtained by a previous template creation. If provided, only the checked parameters in the next column are required. | ✅ (required) |
User Retry
If, for some reason, the user is on the boundary of an age check threshold, you may want the user to retry. You can enable retries so that your users have another chance to perform an age check. You can set parameters at the session and method levels.
Enable retry at the session level:
You will need to set:
Configure retry at the method level:
You will need to specify the number of retries that are allowed for each method individually. For example, 2 attempts for Age Estimation, 1 try for Doc Scan, and 1 try for Digital ID.
Response
If the request is successful and a session is generated, the API will send a response in the form:
Parameter | Description |
|---|---|
| Session ID (UUID). Please share this session ID with us if you raise a support request regarding session issues. |
| The time at which the session will expire. |
| Status of the session. |
Error codes
Below are the error codes when creating a session.
Response code | Description |
|---|---|
200 | Success |
400 | Missing field in post body |
401 | Missing or unknown SDK ID |
403 | Incorrect API key |