One SMS API. Every channel.
One REST endpoint for SMS, plus RCS, WhatsApp and email through the same API, with multi-vendor failover underneath. Authenticate with an API key, define a channel priority per use case, and receive delivery status on your webhooks — if delivery fails, the next channel in your cascade is tried instantly. For OTP-specific flows, see the OTP API.
Channel cascade, handled for you
Send a message via a single API call. You define the channel priority — if delivery fails on the first channel, the next in your configured sequence is tried automatically.
You configure the channel priority and failover sequence. If delivery fails on any channel, the next channel in your configured sequence is tried automatically until the message is delivered.
How it works
Automatic channel failover — if delivery fails, the next channel is tried instantly
Single API endpoint for all channels — SMS, RCS, WhatsApp, Email
Configurable priority and failover sequence per customer or use case
Use your own vendors (BYOV) or our managed routing network
Real-time delivery callbacks with full status reporting
Messages cascade across your configured channels until one succeeds
Built for multi-channel messaging
The Messaging API covers everything that isn't authentication. For one-time passcodes and verification flows, the dedicated OTP API adds attempt tracking, fraud signals, and SMS-to-email cascade.
Notifications & alerts
Order updates, delivery ETAs, account activity — sent via the channel most likely to be read.
Transactional messaging
Receipts, confirmations, and status changes with cascade fallback so the message lands.
Marketing campaigns
Run RCS-first or WhatsApp-first campaigns with SMS fallback for unreachable recipients.
Two-way conversations
Inbound replies routed back through the same API, regardless of which channel delivered.
Ready to integrate?
Get started with our API in minutes. Use your own vendors or our managed network — the API stays the same.