Messaging · RCS
RCS Business Messaging API with a verified, branded sender.
Send carousels, suggested replies, action buttons, and branded, verified business messages on Android's native messaging app. You get higher engagement than SMS and more reach than standalone apps. Cascade to SMS and WhatsApp through the Unified Messaging API for reliable delivery on every device.
Send your first RCS message
Authenticate with your App ID and Key, send one request, and your first rich RCS message goes live with SMS fallback built in. Copy, paste, run.
curl -X POST https://api.enablex.io/rcs/v1/messages \
-u APP_ID:APP_KEY \
-H "Content-Type: application/json" \
-d '{
"type": "text",
"phone": "+14155550100",
"agent": "your-agent-name",
"text": "Hi Alex, your appointment is confirmed for tomorrow at 10:00 AM.",
"suggestions": [
{ "type": "reply", "text": "Confirm", "postback": "appointment_confirmed" },
{ "type": "reply", "text": "Reschedule", "postback": "appointment_reschedule" }
],
"fallback_text": "Your appointment is confirmed for tomorrow at 10:00 AM."
}'
const axios = require('axios');
const res = await axios.post(
'https://api.enablex.io/rcs/v1/messages',
{
type: 'text',
phone: '+14155550100',
agent: 'your-agent-name',
text: 'Hi Alex, your appointment is confirmed for tomorrow at 10:00 AM.',
suggestions: [
{ type: 'reply', text: 'Confirm', postback: 'appointment_confirmed' },
{ type: 'reply', text: 'Reschedule', postback: 'appointment_reschedule' }
],
fallback_text: 'Your appointment is confirmed for tomorrow at 10:00 AM.'
},
{ 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/rcs/v1/messages",
auth=HTTPBasicAuth("APP_ID", "APP_KEY"),
json={
"type": "text",
"phone": "+14155550100",
"agent": "your-agent-name",
"text": "Hi Alex, your appointment is confirmed for tomorrow at 10:00 AM.",
"suggestions": [
{"type": "reply", "text": "Confirm", "postback": "appointment_confirmed"},
{"type": "reply", "text": "Reschedule", "postback": "appointment_reschedule"}
],
"fallback_text": "Your appointment is confirmed for tomorrow at 10:00 AM."
}
)
print(res.json())
What the RCS API includes
Branded sender. Rich cards. Quick replies. Suggested actions. Payment flows. Cascade safety net. One API.
Google Verified Sender
Brand logo, verified badge, and business profile show in the message thread. Same trust signal as the Play Store, but in chat.
Cards & carousels
Single rich cards or swipeable carousels with images, videos, titles, descriptions, and CTA buttons. Up to 25,000 characters per message.
Suggested replies & actions
One-tap quick replies, dial, open URL, calendar invite, share location, and request payment.
Auto cascade to SMS / WhatsApp
If the recipient isn't RCS-capable, fall back to WhatsApp or SMS in the same API call, so the message still arrives on a fallback channel.
Read receipts & analytics
Sent, delivered, read, replied: per message, per template, per campaign. Webhook on every state change, dashboards on every funnel.
Encrypted & opt-in safe
Messages travel over IP with carrier-managed E2E encryption where supported, consent and STOP/START are handled, and local consent rules are applied per country.
Built for the workflows where rich beats plain text
BFSI, retail, logistics, healthcare: the places customers expect more than a 160-character SMS.
Statements & payment flows
Card statements with quick-reply pay, EMI offers with one-tap apply, fraud-alert verification with branded trust signals.
Voice AI for bankingCarousel product drops
Swipeable product carousels in the SMS inbox, with add-to-cart and buy-now CTAs, no app install needed.
Retail and ecommerceDelivery tracking with map
Live ETA cards, driver photo, share-location action, reschedule one-tap, designed to reduce failed deliveries.
AI for customer supportAppointments & results
Visit cards with map and calendar add, lab-result alerts with secure portal link, refill reminders with one-tap renewal.
Voice AI for healthcareBoarding pass & updates
Boarding-pass cards, gate-change push, ancillary up-sell with one-tap purchase. Native to the SMS app, no new install.
Talk to salesPlan upgrades & renewals
Branded recharge prompts, plan-comparison cards, one-tap renewal. Replaces generic SMS with operator-branded experience.
Talk to salesThe trust of a verified brand. The interactivity of an app. Inside the SMS inbox.
RCS turns the most-opened app on Android, the messaging app, into a branded surface for your business, with your logo, verified badge, brand colour, rich cards, carousels, and one-tap actions. Nothing for the customer to install.
- Google Verified Sender registration handled end-to-end: brand logo and verified badge in every message.
- Single rich cards and swipeable carousels with image / video / title / description / multiple CTA buttons.
- Suggested replies and suggested actions: dial, open URL, share location, calendar invite, request payment.
- Auto-cascade: if device isn't RCS-capable, the same payload falls back to WhatsApp or SMS, all from one API call.
- Direct carrier RCS routes in our core markets plus Google Jibe globally.
Why teams build RCS on EnableX
What sets the EnableX RCS API apart.
Direct and global RCS routes
Direct carrier RCS routes in our core markets plus global coverage, with Verified Sender registration handled by EnableX.
One API, three channels
RCS first, WhatsApp fallback, SMS as the last resort, all in a single API call. No stitching. No three vendors. No duplicate billing.
Full-stack: SMS + WhatsApp + RCS + Voice + Video
One platform, one bill, one SLA. On-prem deployment available for BFSI, government, and sovereign requirements.
Pay-as-you-use RCS. Cascade billed only once.
RCS API FAQs
Build with RCS Messaging API: Developer Docs
See EnableX in action.
Talk to sales, or start a free trial. No credit card required.
Free trial credits · No credit card · API keys in 2 minutes