Skip to main content
Sandbox is Notifique’s flight simulator: you practice the full integration without risking a real message or spending credits.

​
What is sandbox?

It’s Notifique’s test environment. The API is the same (https://api.notifique.dev/v1/...); what changes is how the message is handled — by key (sk_test_) or by workspace test destination. Think of a flight simulator: same cockpit, same maneuvers, nobody actually takes off.

​
What is it for?

With sandbox you can:
  • Integrate your app without sending real SMS, email, or WhatsApp
  • Test webhooks, templates, and flows before go-live
  • Preview messages in the Sandbox inbox (bubble, HTML, push, RCS, voice)
  • Validate email HTML with the Compatibility checker
  • Simulate delivery status (delivered, read, failed) in the Sandbox inbox
  • Validate payloads and errors without debiting credits
Nothing in sandbox affects production data or sends.

​
Two ways into sandbox

Do not mix sandbox and real recipients in one request → 422 SANDBOX_MIXED_RECIPIENTS. Do not use another workspace’s sandbox email or phone → 422 SANDBOX_IDENTITY_FOREIGN.

​
Test destinations per workspace

Each workspace has fixed identities derived from its slug at creation: In the dashboard: Developer → Sandbox inbox → Your test destinations (copy email, phone, and device). Send composers (New email, SMS, etc.) show the same shortcut. Example with a production key — only intercepted if the destination matches:
With sk_test_, any to works; the From domain does not need to be verified.

​
When to use?

​
How to use

​
1. Create a test key (optional)

Open Developer → API Keys, create a Sandbox key, and copy sk_test_... immediately. Need help? See API Keys. With workspace test destinations, you can also use sk_live_ without sending anything to the customer.

​
2. Call the API as usual

Same URL, same endpoints. Change the key or recipient:
No extra environment header.

​
3. Track in the Sandbox inbox

Open Developer → Sandbox inbox. There you can:
  • Preview each message in the Preview tab (like production detail)
  • For email, use the Compatibility tab (HTML checker: CSS, images, links, deliverability)
  • Review raw payload and metadata (Details, Payload)
  • Release scheduled messages with Release now
  • Simulate status: delivered, read, click, failed (per channel)
  • Browse webhook examples per channel in the Webhooks tab

​
4. Test webhooks

Events use the same names as production. The payload includes sandbox: true in data so you can filter on the same endpoint. Destination-intercepted sends include intercepted: true in inbox metadata. More in Webhooks.

​
5. Templates and email in sandbox

  • Template editor: Template preview test → Sandbox destination → message in the inbox, no real provider or billing.
  • API: POST /templates/:id/send-test with "sandbox": true (dashboard) or POST /v1/templates/send with test destinations / sk_test_.
  • Email: POST /v1/email/messages or Email → New email in the dashboard; HTML preview and compatibility checker in the composer.
Template details: Variables and CRUD.

​
6. Go to production

When ready, use real recipients with sk_live_.... Like switching from the simulator to the real flight.

​
What works and what doesn’t

​
Official WhatsApp (Cloud API) in sandbox

With sk_test_, POST /v1/whatsapp/messages and POST /v1/templates/send do not call Graph or the Meta payment gate:
  • No token ping → does not mark the real instance as DISCONNECTED
  • No real META_PAYMENT_METHOD_REQUIRED / META_TEMPLATE_REQUIRED
  • The payload shows up in the Sandbox inbox like other channels
Use production (sk_live_) to validate an approved template, the 24h window, and a card in WhatsApp Manager. Details: Official Meta templates.
Operations that depend on a real provider (WhatsApp QR, Instagram connection) may return 403 or 501 in sandbox.

​
Limits

​
Sandbox vs production

​
Next steps

  • Start here: send your first test message
  • API Keys: create and use sk_test_ and sk_live_
  • Webhooks: receive simulated events on your server
  • Templates: test multichannel in sandbox