Send your first message in the sandbox.

What you get

• Durable acceptance

  A 202 means the message and its first job are stored together. It is accepted, not yet delivered.

• Environments by key

  hw_test_ keys use the Sandbox and hw_live_ keys use Live. The key decides, never a request flag.

• Tenants on every request

  Name the tenant on each send, or use a key limited to one tenant.

• References for beta customers

  An OpenAPI reference, a TypeScript quickstart, and error-code and webhook references.

• Public docs and changelog

  At launch

  A public docs site with tested examples, a changelog, AI-readable pages and a docs assistant.

• Status page

  At launch

  Platform status and incident history.

• Configuration releases

  Release 2

  Validate, diff, promote and roll back templates and policies from CI.

How it works

1. Get a Sandbox key

   Create an API key in the Sandbox environment from the dashboard.

2. Install the SDK

   Add @round-robin-solutions/hopwire to your Node backend.

3. Send with a scenario

   Call messages.send with a sandbox scenario such as whatsapp_fails.

4. Handle the webhook

   Verify the signature and act on message.delivered or message.failed.

5. Go live

   Once your WhatsApp and SMS connections and templates are approved, switch to a Live key.

Questions

Related

• APIAvailableA versioned JSON API at api.hopwire.io for messages, templates, tenants, senders, webhooks and usage, with idempotency and cursor pagination.
• SDKAvailableA typed server-side SDK for Node with automatic idempotency keys, careful retries, typed errors and a webhook verifier.
• SandboxAvailableA sandbox with simulated providers and fixed scenarios for failures, timeouts and messy callbacks, using the same webhooks as Live.
• WebhooksAvailableStandard Webhooks signatures, at-least-once delivery, event IDs to deduplicate on, secret rotation and replay.