Sandbox
Instant sandbox: no account
POST https://api.app2email.com/v1/account/sandbox(no key, no body) answers a key for the demo number12025550100. MCP:create_sandboxon the Management MCP server.- Send a template to a pretend customer:
POST /v1/12025550100/messages. Nothing reaches WhatsApp. GET /v1/12025550100/events?wait=25returnsmessage.statussent, delivered, read, then the customer's answer asmessage.received.
| 12025550101 | Ava answers every message a few seconds later. |
| 12025550102 | Ben reads and never answers: a free-form message to him is 422 outside_24h_window. |
| 12025550103 | Cara: delivery fails (message.status failed, message.failed). |
| 12025550104 | Dan answers STOP: contact.opted_out, then a marketing template to him is 403 recipient_opted_out. |
| 12025550105 | Eve asks for a person: set the conversation's owner to human. |
It has GET /me, GET /templates, POST /messages, GET /messages, GET /conversations, PUT /conversations/{contact}/owner, GET /events and POST /sandbox/inbound (a pretend customer writes now). Templates are checked by the same code as on a real number. Any other call: 403 not_in_instant_sandbox. A key lasts 7 days; its messages are kept 24 hours after the last call.
Sandbox key on your own number
- Create a key with Sandbox on (API key page), or a temporary key in the console.
- Same URL, same calls:
POST /v1/{number}/messagesanswers"sandbox": true, idswamid.SANDBOX.…. - Webhooks get
message.statussent, delivered, read within seconds.
/v1/account/… and /v1/partner/… take an account or partner key, not a number key: no sandbox there.
simulated 4
every check runs for real; nothing reaches WhatsApp; the answer has "sandbox": true, ids start wamid.SANDBOX., message.status events follow
refused 125
answers 403 sandbox_key; use a live key
reads 130
reads real data
real change 24
changes real data, also with a sandbox key