Introduction

The Age Verification Sandbox is an isolated test environment that lets you simulate age verification outcomes so you can validate your integration without running live checks. You can either simulate user activity via the Sandbox interface or bypass the UI by using API calls to mock responses. A typical flow is to create an age verification sandbox session, set the expected outcome, and retrieve the results from the Yoti API. This documentation also covers the steps required to send API requests using Yoti’s Central Authentication service, which is required for the AVS sandbox.

A session represents a single end-to-end interaction with the Yoti age verification service. You’ll receive the session ID in the response when you create a session. Each time a user on your app or website initiates an age verification, you should create a new session with Yoti.

With the sandbox, you have two primary options:

• You can use the simple sandbox UI to set the response and trigger a redirect to your callback.

• Alternatively, you can bypass the UI completely by using the API endpoint to set the mocked response directly.

The sandbox does not perform any real age verification checks. Unlike the production API, only mocked responses are returned—including the user's age, the result of the check, the verification method, and other session parameters.

Optionally, you can subscribe to webhook notifications, just like in the production API. The sandbox will send a POST request with a basic notification payload to your endpoint each time a mocked check completes. For the full session details, you can use the session ID to fetch the complete results from the sandbox endpoint.