Sandbox · developer access

Developer sandbox

Apply for credentials, get approved, and try the real API against your own isolated sandbox tenant: seeded data, simulated media, no risk to a live desk.

What your sandbox gives you

Scoped credentials

Your key is tied to an isolated sandbox tenant: no production data, no shared state with anyone else.

Seeded scenarios

A pre-populated desk: lines, hoots, and a conference, so your first call has something real to connect to.

The real control plane

The same API and the same event WebSocket. You build against the contract you'll ship on.

Full documentation

The developer guide, the interactive API explorer, the OpenAPI spec, and the TypeScript SDKs, all linked from your dashboard.

What's real vs simulated

RealSimulated
The REST contract & response shapesMedia: calls connect against a mock mixer, no live RTP billed
The event WebSocket & frame formatsCarrier (PSTN) ingress/egress: no real numbers dialed
Auth, roles, and tenant isolationRecordings: generated fixtures you can fetch and verify
State machines & error codesPresence: scriptable, so you can drive your UI deterministically

Limits

  • Rate limits are tighter than production.
  • No real PSTN connectivity and no billable media.
  • Sandbox keys never work against a production tenant, and vice versa.