Test the failures before your users find them.

What you get

• Scenarios on demand

  Delivered, read, WhatsApp fails, WhatsApp times out, rejected, all channels fail, unknown submission and throttled once.

• Messy callbacks too

  Duplicate and out-of-order provider reports, so you can prove your webhook handler copes.

• Same webhooks as Live

  Same event schema and the same signatures, so the code you test is the code you ship.

• Kept apart from Live

  Sandbox keys start with hw_test_. Test controls on a Live key are rejected, and Sandbox resources cannot reference Live ones.

• Test clocks

  At launch

  Move time forward to test schedules, retries and expiry without waiting.

• Shared WhatsApp sandbox number

  At launch

  Send real WhatsApp messages to joined testers before you have your own WhatsApp Business account.

How it works

1. Use a Sandbox key

   Create a key in the Sandbox environment.

2. Pick a scenario

   Add sandbox.scenario to a send, such as whatsapp_timeout.

3. Watch it play out

   Follow the attempts in the explorer and the events at your webhook.

Questions

Related

• Developer overviewAvailableHow Hopwire fits into your backend: a REST API, a TypeScript SDK, signed webhooks and a sandbox with fixed failure scenarios.
• WebhooksAvailableSigned events for delivery, replies, opt-outs, template changes and sender restrictions, retried for about three days and replayable.
• DevelopersAvailableA typed SDK, idempotent sends, stable error codes, signed webhooks and a sandbox that simulates the hard failures.