RCS API for business messaging
What is an RCS API?
An RCS API is an HTTP interface your application calls to send rich business messages in code: you make one authenticated request with a destination number and a payload — plain text, a rich card, or a carousel of cards — and the API delivers it natively in the recipient's default messaging app with your verified business name, logo, and color. Orbit by Devotel's RCS API does that over a single POST to /api/v1/messages/rcs via the DotGo RBM Hub, supporting rich cards, carousels of 2–10 cards, and suggested reply and action chips, with a capability check per recipient and automatic SMS fallback for devices that cannot receive RCS. RCS runs alongside SMS, WhatsApp, email, voice, AI agents, and a built-in contact center on one platform and one pay-as-you-go bill.
Send your first RCS message from code
One authenticated request sends a rich message. Authenticate with your API key in the X-API-Key header, post the destination number and a body, and attach chips either as plain-text suggested_replies on a text send, or inside the card payload on a rich send.
curl -X POST https://api.orbit.devotel.io/api/v1/messages/rcs \
-H "X-API-Key: $ORBIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+14155552671",
"body": "Your order #12345 has shipped!",
"suggested_replies": [
{ "action": { "text": "Track Order", "open_url": { "url": "https://example.com/track/12345" } } },
{ "reply": { "text": "Contact Support", "postback_data": "contact_support" } }
]
}'A standalone rich card — image, title, description, and action buttons in a single message:
curl -X POST https://api.orbit.devotel.io/api/v1/messages/rcs \
-H "X-API-Key: $ORBIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+14155552671",
"rich_card": {
"card_content": {
"title": "Nike Air Max 90",
"description": "$129.99 — Free shipping on orders over $50",
"media": {
"height": "MEDIUM",
"content_info": { "file_url": "https://example.com/images/shoe.jpg" }
}
},
"suggestions": [
{ "action": { "text": "Buy Now", "open_url": { "url": "https://example.com/buy/shoe" } } },
{ "reply": { "text": "More Details", "postback_data": "details_air_max_90" } }
]
}
}'Text, rich card, and carousel are mutually exclusive message shapes — the chips belong inside the card payload on a rich send. Delivery, read, and click events post to your webhook in the same shape as every other channel.
What the Orbit RCS API does
| Capability | What you get |
|---|---|
| Send rich cards over one HTTPS call | One authenticated POST sends a rich card — a title, a description, and a media file with per-card suggestion chips — from code. No carrier relationship, no SMPP bind, no messaging infrastructure to stand up. |
| Carousels of 2–10 cards | Send a horizontally scrollable rich-card carousel with per-card chips and an optional message-level suggestions row — product catalogs, location pickers, and multi-offer promotions render natively in the messaging app. |
| Suggested replies & actions | Attach up to 11 chips per send. A reply chip sends a text back as a user message and delivers postback data to your webhook; an action chip opens an HTTPS URL, dials a number, or opens a map location. |
| Verified sender branding | Register your brand and agent once — brand and agent travel to the carrier gateway together — and every RCS send renders under your verified business name, logo, and brand color in the chat thread. |
| Per-recipient capability check | Probe a recipient's RCS capability before spending a send, or let the send path check inline. Positive verdicts are cached for 24 hours, and a not-capable response carries the fallback hint so you can route down the SMS path in the same decision. |
| Automatic fallback to SMS | Turn on the org-level fallback chain once — e.g. RCS falls through to SMS — and every RCS send transparently retries the next channel when a recipient cannot receive RCS, re-running the SMS opt-out and do-not-call check before it delivers there. |
| Brand-to-launch onboarding | Register the brand, create the agent, submit carrier verification evidence, and launch — four ordered gates with pollable status, from the dashboard or the API. Tester devices can preview rich cards before any carrier approves the agent. |
| Delivery and read receipts | Queued, sent, delivered, read, and click events post to your webhook as they happen, so your app knows what landed without polling. Template analytics report delivery, read, and click rates per template. |
| One API, every channel | The same integration also carries SMS, WhatsApp, email, and voice, with shared contacts, campaigns, and flows — so adding a channel is a routing change, not a new integration and a second bill. |
Know your reach before you send
RCS reach is per handset and per carrier — a recipient's device either can or cannot receive a rich message, and the answer changes by market. Probe a single number's capability from the API, or paste a whole contact list into the free reach checker and get back the share of numbers that can receive RCS — before you commit a campaign budget.
RCS vs SMS vs WhatsApp — where each channel fits
SMS — the floor
Every handset on earth, plain text, no branding. Use it as the fallback channel every program still needs, and the minimum viable reach guarantee.
RCS — the upgrade
Verified branding, rich cards, and chips in the default messaging app on Android, with carrier verification rather than a separate business-account install. Capable handsets get the upgrade; the rest fall through to SMS.
WhatsApp — the install base
Rich, branded, two-way messaging to the installed WhatsApp user base, onboarded through the WhatsApp Business Platform. Both run behind Orbit's one API — pick the channel per market, not per vendor.
For the detailed evaluation, see RCS vs WhatsApp for business messaging and the RCS launch checklist.
Built for rich business messaging
Order & delivery notifications
Ship a branded order confirmation with a Track Order action chip and a Contact Support reply, and let the click and read receipts tell you which recipients engaged — no app install required.
Product carousels & commerce
Card 2–10 products into a carousel with a Buy Now chip per card and a message-level checkout chip. The same product catalog also feeds WhatsApp, so the catalog connect is done once for both channels.
Appointment reminders with actions
Send a reminder with Confirm and Reschedule chips and fall back to SMS automatically for recipients whose devices cannot receive RCS — the message still lands, on the channel the device supports.
Marketing campaigns over verified branding
Send rich promotions under your verified business name and brand color — the presentation layer that makes a marketing message look trusted — and measure template-level delivery, read, and click rates.
Orbit vs Infobip vs Twilio vs Sinch for RCS
| Feature | Orbit | Infobip | Twilio | Sinch |
|---|---|---|---|---|
| RCS Business Messaging | ||||
| RCS on the GSMA Universal Profile | ||||
| Verified sender / branded RCS agent | ||||
| Rich cards, carousels & suggested replies | ||||
| Automatic SMS fallback when RCS is unavailable | ||||
| Native AI agents on RCS | ||||
| Beyond RCS | ||||
| WhatsApp, email & embeddable video on one platform | ||||
| Programmable voice + AI voice agents | ||||
| Published pay-as-you-go pricing, self-serve signup | ||||
| One platform & one bill across every channel | ||||
Comparison data as of Q3 2026. Competitor feature details sourced from public vendor documentation, G2, and Gartner Peer Insights. Subject to change at the vendor's discretion. Yes Partial No
What it costs
Pay-as-you-go with no monthly platform fee — you pre-pay credits and pay only for what you send. US RCS is published at $0.01 per message; volume rate cards are available on request, and a message that falls back to SMS is billed at the SMS rate.
RCS API — frequently asked
- What is RCS for Business?
- RCS (Rich Communication Services) for Business is the carrier-backed upgrade to SMS on the GSMA Universal Profile. It adds a verified, branded sender, rich cards and carousels, suggested replies, and read receipts, delivered to the native messaging app — with automatic SMS fallback for devices that cannot receive RCS.
- Does RCS fall back to SMS?
- Yes, with a provider that supports it. When a recipient's device or network cannot receive an RCS message, Orbit falls back to SMS automatically so the message still lands, and you are billed for the channel actually used.
- How do I send my first RCS message from code?
- Make a single authenticated POST to /api/v1/messages/rcs with the destination number and a body — or a rich_card or rich_card_carousel payload — using your API key in the X-API-Key header. You can preview the rich payload on a tester device before your agent is launched, and a public tester-account flow lets you try it on one handset before you register a brand at all.
- How do I become a verified RCS sender?
- Register a brand in the dashboard or over the API, create the agent (bot) on that brand, submit the carrier verification evidence (conversation screenshots and KYC documents), and launch. The brand and agent travel to the carrier gateway in one combined registration, and carriers typically adjudicate in 3–5 business days. Until a carrier launch lands, an unlaunched agent can still message registered tester devices.
- What happens when a recipient cannot receive RCS?
- Orbit checks per-recipient capability before the send — from its 24-hour capability cache or a live probe. A not-capable recipient short-circuits the RCS send; if you have the org-level fallback chain enabled (RCS → SMS, or a longer chain), the same message body is retried on the next channel, with the SMS opt-out and do-not-call check re-run before it is delivered there. Without a chain the send fails closed with a delivery receipt you can read.
- RCS vs WhatsApp — which should I use?
- Both deliver rich, branded, two-way messaging; the difference is reach and onboarding. RCS renders in the recipient's default messaging app on Android with no separate install, and its onboarding path goes through carrier verification rather than a WhatsApp Business Account. Orbit ships both behind one API and one bill — evaluate them per market: the RCS reach checker tool estimates what share of a contact list can receive RCS before you commit a campaign.
- How much does the Orbit RCS API cost?
- Orbit is pay-as-you-go with no monthly platform fee: you pre-pay credits and pay only for what you send. RCS is published at $0.01 per message (US); volume rate cards are available on request.
Explore more
Start sending over the API
RCS is one channel of Orbit by Devotel — SMS, WhatsApp, email, voice, video, AI agents, and customer data on one platform and one pay-as-you-go bill. Start free, or talk to our team about a volume rate card.