One REST API for SMS, WhatsApp, and Email. Idempotent endpoints, signed webhooks, sub‑second delivery, and the observability your on‑call team actually wants. Built for engineers who'd rather ship than integrate.
SMS, WhatsApp, and Email share the same request shape, the same error taxonomy, and the same webhook schema. Send once — route, fall back, and observe everything in one place.
Predictable resources. Idempotency keys by default. Cursor pagination. Error shapes that tell you what to do, not just what broke. The kind of API that makes onboarding a junior engineer feel like a non-event.
Node, Python, Go, Ruby, PHP, Java, .NET — all generated from the same OpenAPI spec, all versioned together.
Pass an Idempotency-Key and
never worry about double‑sends on retry. 24h replay window.
HMAC‑SHA256 signatures, exactly‑once delivery with replay protection, and a built‑in retry curve up to 24h.
Toggle a single header to route every request through the sandbox. No carriers, no inboxes — just deterministic responses for CI.
Multi‑region active‑active routing, automatic carrier failover, and a queueing layer that gracefully absorbs your traffic spikes. The boring parts are our job.
Requests land at the nearest POP, get authenticated and validated at the edge, then traverse a single hop to the optimal carrier route — typically under 80ms.
Bursty traffic is shaped into per‑channel queues — you keep posting, we keep draining.
We pay 18 carrier partnerships so you don't have to. Routing decisions are made per‑destination, every time, with live signal from past 60s.
Per‑request trace from API call to carrier ACK, with searchable history, cost breakdown, and 30‑day retention on the free tier.
Real‑time delivery, drill‑down on every failure, and search that goes back six months. Wired to PagerDuty, Slack, Datadog — or your own webhook.
Spin up an API key, paste the snippet, and watch the webhook fire. No demo call required, no SDK to compile — just an endpoint that already speaks the language you wrote your app in.