Sandbox environment

You can test your integration in the sandbox environment before moving to production.

The sandbox environment is available for all non-production use cases. It provides access to the same API features as production, while being fully isolated from production data. This allows you to develop and test safely without polluting your region’s live data.

Supported routes

The sandbox environment currently supports all routes under /api/v2/candidates. If the x-api-sandbox header is set for other routes, it will be ignored.

Confirm sandbox mode through the meta property in the API response:

{
  "statusCode": 200,
  "message": "Successfully retrieved ...",
  "data": { ... },
  "meta": {
    "sandboxEnabled": true
  }
}

Enable the sandbox

You can enable the sandbox in one of two ways:

Use the /sandbox endpoint prefix

Replace /v2 with /sandbox in the API endpoint.

https://onderwijsregio.onderwijsin.nl/api/sandbox/schema

Set a request header

Include the following header in your request:

x-api-sandbox: true

Understand data scope and persistence

Sandbox data is scoped to your region. This means that any API key belonging to the same region has access to the same sandbox data.

To prevent an excessive buildup of test data, the sandbox is cleared automatically once per day. As a result, any test data you create should be considered temporary and may be gone the next day.

Know the differences from production

Almost all production rules, conventions, and constraints—including rate limits—also apply in the sandbox.

The primary goal of the sandbox is to offer an environment that behaves as closely as possible to production, while keeping your region’s production data clean and unaffected.

Verify sandbox requests

You can confirm that a request was executed against the sandbox environment in two ways: