Skip to main content

​
Overview

Sandbox mode lets you test the full media buying lifecycle — product discovery, campaign creation, creatives, execution, and delivery — without real platform calls or spending real money. Just create a sandbox advertiser and everything else is handled automatically.

Safe Integration Testing

Validate your workflows end-to-end before going live. No real bids, no real spend.

Fully Automatic

Create a sandbox advertiser and you’re done. Account routing and environment isolation are handled for you.

​
How It Works

Sandbox is account-level, not per-request. The seller provisions a dedicated sandbox account, and every request using that account is automatically treated as sandbox. This eliminates the risk of accidentally mixing real and test traffic in a multi-step flow. When you create an advertiser with sandbox: true:
  • All discovered accounts for that advertiser are sandbox accounts
  • The correct sandbox account is automatically injected into every ADCP call — create_media_buy, get_media_buy_delivery, and get_products
  • Delivery and reporting data are fully scoped to the sandbox environment
  • Responses contain simulated but realistic data
There is no additional configuration needed. You use the same endpoints and workflows as production — the only difference is the sandbox: true flag on the advertiser.
For protocol-level details on how sandbox mode works, see the AdCP Sandbox documentation.

​
Creating a Sandbox Advertiser

​
Via API

Set sandbox: true in the create advertiser request body: 
curl -X POST "https://api.interchange.io/api/v2/buyer/advertisers" \
  -H "Authorization: Bearer your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Acme Corp (Sandbox)",
    "description": "Integration testing advertiser",
    "sandbox": true
  }'
Response: 
{
  "data": {
    "id": "adv_abc123",
    "name": "Acme Corp (Sandbox)",
    "description": "Integration testing advertiser",
    "status": "active",
    "sandbox": true,
    "createdAt": "2026-02-22T21:35:44Z",
    "updatedAt": "2026-02-22T21:35:44Z",
    "linkedBrand": null,
    "brand": null,
    "brandWarning": null
  }
}

​
Via UI

When creating an advertiser in the dashboard, toggle the Sandbox switch before saving. Sandbox advertisers are shown with a badge in the advertiser list for easy identification.
Sandbox is permanent. Once an advertiser is created with sandbox: true, the flag cannot be changed. This protects against accidentally switching an advertiser from sandbox to production after campaigns have been configured.

​
Using Sandbox

Once you have a sandbox advertiser, the entire workflow is identical to production. Discover products, create campaigns, add creatives, and execute — all using the same API endpoints. The sandbox routing is completely transparent. For example, executing a campaign: 
curl -X POST "https://api.interchange.io/api/v2/buyer/campaigns/{campaignId}/execute" \
  -H "Authorization: Bearer your-api-key" \
  -H "Content-Type: application/json"
Because the campaign belongs to a sandbox advertiser, all ADCP calls are automatically routed through the sandbox environment. Responses are simulated — no real bids are placed and no real spend occurs.

​
Murph Sandbox Test Plans

When Murph is enabled for an account, GET /api/v2/murph/test-runs returns the latest sandbox test plans and diagnostics that appear in Murph’s right rail. This endpoint is scoped to the authenticated customer and requires the ask-murph feature flag. Query parameters:
ParamNotes
takeNumber of plans to return, 1..20. Defaults to 5.
Each item in runs[] includes the plan status (planned, partial, passed, or failed), the current stage, sanitized summary, artifacts, and diagnostics, plus timeline steps[] with operation names, HTTP status when available, and a diagnostic message. Murph currently records buyer-stack plans and approval-blocked attempts; executable buyer-stack runs require a server-issued approval token flow. Per-agent discovery diagnostics may appear in diagnostics.agentCalls when they are available. These are safe summaries only, not raw upstream responses.

​
Filtering Sandbox Advertisers

The sandbox field is returned on every advertiser response. Use the optional sandbox query parameter to filter: 
# List only sandbox advertisers
curl "https://api.interchange.io/api/v2/buyer/advertisers?sandbox=true" \
  -H "Authorization: Bearer your-api-key"

# List only production advertisers
curl "https://api.interchange.io/api/v2/buyer/advertisers?sandbox=false" \
  -H "Authorization: Bearer your-api-key"
In the dashboard, sandbox advertisers are shown with a Sandbox badge so they are easy to distinguish from production advertisers at a glance.

​
Key Constraints

ConstraintDetail
Immutable flagsandbox cannot be changed after advertiser creation
Strict isolationSandbox and production data are fully isolated — no risk of mixing test and real traffic
No silent fallbackIf sandbox execution cannot proceed, the API returns an explicit error rather than falling back to production

​
Next Steps

Advertiser API Reference

Full schema for POST /advertisers, including the sandbox field.

AdCP Sandbox Docs

Protocol-level details on how sandbox mode works in AdCP.

Quickstart

Get up and running with the Interchange API.