Unified Messaging API
A unified messaging API is a single endpoint that sends a message over WhatsApp, SMS or RCS and falls back automatically when the first channel cannot deliver. The EnableX Unified Messaging API checks each recipient's channel capability, delivers on the best one, and returns one delivery-receipt format across all three, in 50+ countries.
One integration for WhatsApp, SMS and RCS. Set a channel order, send once, and the platform checks each recipient, delivers on the best channel and falls back when it has to. One delivery-receipt format, one number pool, one bill.
Send across channels with one call
Authenticate, post one request with the channel order you want, and the platform cascades the message from WhatsApp to SMS. Copy, paste, run.
curl -X POST https://api.enablex.io/messaging/v1/messages \
-u APP_ID:APP_KEY \
-H "Content-Type: application/json" \
-d '{
"to": "+14155550100",
"channels": ["whatsapp", "sms"],
"preference": "order",
"whatsapp": {
"type": "text",
"recipient_type": "individual",
"text": { "body": "Your order #7821 has shipped. Track at: https://yourapp.com/track/7821" }
},
"sms": { "from": "ENABLEX", "data_coding": "plain" }
}'const axios = require('axios');
const res = await axios.post(
'https://api.enablex.io/messaging/v1/messages',
{
to: '+14155550100',
channels: ['whatsapp', 'sms'],
preference: 'order',
whatsapp: {
type: 'text',
recipient_type: 'individual',
text: { body: 'Your order #7821 has shipped. Track at: https://yourapp.com/track/7821' }
},
sms: { from: 'ENABLEX', data_coding: 'plain' }
},
{ auth: { username: 'APP_ID', password: 'APP_KEY' } }
);
console.log(res.data);import requests
from requests.auth import HTTPBasicAuth
res = requests.post(
"https://api.enablex.io/messaging/v1/messages",
auth=HTTPBasicAuth("APP_ID", "APP_KEY"),
json={
"to": "+14155550100",
"channels": ["whatsapp", "sms"],
"preference": "order",
"whatsapp": {
"type": "text",
"recipient_type": "individual",
"text": {"body": "Your order #7821 has shipped. Track at: https://yourapp.com/track/7821"}
},
"sms": {"from": "ENABLEX", "data_coding": "plain"}
}
)
print(res.json())Everything an omnichannel messaging programme needs
One integration, per-recipient routing, automatic fallback, native rendering per channel and one receipt schema.
Per-recipient channel selection
The platform checks RCS capability, WhatsApp reachability and SMS reachability for each recipient, then routes to the best channel.
Automatic fallback
RCS, then WhatsApp, then SMS, or any order you define. Billed per delivered message, not per attempt.
Native rendering per channel
One payload, three renders: a rich card on RCS, a template on WhatsApp, plain text on SMS.
Unified delivery receipts
Sent, delivered, read, replied and failed in one JSON schema across all channels. Signed webhooks with retries.
Campaign Manager on the same account
Marketing launches broadcasts from Campaign Manager; engineering ships flows in code. Same account, same numbers, same receipts.
Rules applied per channel
Template approval, sender registration and opt-in rules applied per channel and per country, so the right rule runs every time.
Built for messages that must arrive
Where one channel is never enough.
Send once. The platform picks the channel.
Many "omnichannel" APIs are three APIs behind one login. This is one endpoint that checks capability per recipient, delivers, falls back and bills once per delivery.
- Capability check per recipient in milliseconds: RCS, WhatsApp or SMS reachable?
- Configurable order per message type: OTP on SMS, marketing on RCS, conversation on WhatsApp.
- One number pool, one bill, one dashboard.
- Native rendering per channel and one signed receipt schema across all of them.
Why teams build messaging on EnableX
What sets the EnableX Unified Messaging API apart.
Direct routes
Direct carrier and Meta connections in our core markets, with sender registration and local compliance handled per country.
Deployment and white-label
Run the platform on our cloud, your cloud, a private cloud or fully on-premise, or under your own brand as a telco or reseller.
Full-stack
Add a voice OTP fallback or a video escalation from the same account, and put an AI agent on any channel with human handover.
Where teams use the Unified Messaging API
Unified Messaging API FAQs
Build it: developer docs
Prerequisite → Unified Messaging API → Notification Webhook →
See EnableX in action.
Start a free trial, or talk to sales about volume pricing and on-premise. No credit card required.
Free trial credits · No credit card · API keys in minutes