Sandbox Environment

The sandbox serves a static ad catalogue embedded at startup, returning the top semantic matches for each request in the same response schema as production. Use it to build and verify your integration before pointing at production.

Base URL

https://sandbox.adzen.ai

Endpoints

No billing events are generated by any sandbox call.

Getting a sandbox key

Ask your Adzen account representative. Sandbox keys are scoped to a single product in the same way production keys are.

Requests without a valid key return 401 on sandbox exactly as they do in production, so authentication failures surface during development rather than at cutover.

Example

curl -X POST https://sandbox.adzen.ai/ugc/v1/process \
  -H 'Content-Type: application/json' \
  -H 'X-API-Key: YOUR_SANDBOX_KEY' \
  -d '{
    "post_id": "thread-12345",
    "message": "Looking for a good plumber in Seattle",
    "geo_target": { "state": "US-WA" }
  }'

Check the health endpoint first. It needs no key and confirms you can reach the environment at all:

curl https://sandbox.adzen.ai/ugc/health

Testing the no-match path

About one in five sandbox UGC requests returns the no-match body instead of ads, so your client meets it during development:

{ "no_ad_retry_after_seconds": 86400 }

This body has no ads field. See No match for how to handle it.

Testing failure paths

To exercise your error handling, send a deliberately malformed request:

Because responses are schema-identical to production, the same client code handles both environments.

Before you go live: production is US-only