Sandbox▾
Sandbox
What the documentation sandbox does, what it does not do, and how to tell its responses apart from real ones.
Simulated, not live
The Try it panels in this documentation call endpoints hosted on this site that return canned data. They never contact Meta, never send a WhatsApp message, and never store anything you type.
Telling sandbox responses apart
- Every response body has a top-level
"sandbox": true. - Every response carries the header
X-Sendport-Sandbox: true. - Sandbox responses are also
X-Robots-Tag: noindex, nofollow. - Ids are derived from your input, so the same request always returns the same ids.
The sandbox key
Any well-formed key works: it must match sp_test_… or sp_live_…. The panels default to sp_test_sandbox. Send no header, or a malformed one, and you get the real 401 envelope — which is the point.
What is not simulated
| Behaviour | Sandbox |
|---|---|
| Message delivery | Never — status stays accepted |
| Webhook delivery | Never — payloads are documented, not sent |
| Persistence | None — nothing written, list endpoints return fixtures |
| Rate limiting | Headers are returned, but no limit is enforced |
| Template review | Always APPROVED |