Announcing RCS rich messaging in the Sinch Engage Messages API
From 18 November 2026, developers can send RCS messages through the Sinch Engage Messages API. That includes tappable suggestions, images and files, rich cards, carousels and location pins, with an optional SMS fallback.
| Announced on | Available from | Applies to |
|---|---|---|
| 17 November 2026 | 18 November 2026 | Sinch Engage accounts enabled for RCS that send messages with the Messages API, in every country where RCS is available (see RCS overview) |
What's new?
Until now, RCS was only available in the Sinch Engage Hub. You can now send RCS from the same Messages API endpoint you already use for SMS, MMS, and TTS (POST /v1/messages).
-
RCS text. Set
formattoRCSand sendcontentof up to 2,000 characters. - Tappable suggestions. Add up to 10 buttons under an RCS text message: quick reply, open a link, call a number or show a location. Each button label can be up to 25 characters.
- Images and files. Send an image or file, with an optional thumbnail and file name.
- Rich cards. Send a card with a title (up to 200 characters), a description (up to 2,000 characters), media and up to 4 buttons.
- Carousels. Send 1 to 10 cards the recipient swipes through. Each card can have up to 4 buttons, plus up to 3 buttons for the whole carousel.
- Location pins. Send a map pin with a title and an optional label.
- Optional SMS fallback. Add a plain-text SMS to send if the recipient can't receive RCS.
Each message carries either text (with optional suggestions) or one piece of rich content: an image or file, a card, a carousel or a location pin.
Nothing changes for existing SMS, MMS or text-to-speech integrations, or for accounts that use RCS upscaling today.
When does SMS fallback happen?
SMS fallback only happens when you include fallback_message and the recipient can't receive RCS. We never send an SMS on your behalf unless you ask for it.
| What you send | Recipient can receive RCS | Recipient can't receive RCS |
|---|---|---|
An RCS message, with fallback_message
|
Sent as RCS |
fallback_message.content is sent as SMS |
An RCS message, without fallback_message
|
Sent as RCS | Not delivered. The delivery report shows the outcome |
Plain text with format: "SMS" or no format, and RCS upscaling on |
Sent as RCS, as today | Sent as SMS, as today |
Plain text with format: "SMS" or no format, and RCS upscaling off |
Sent as SMS | Sent as SMS |
A message is an RCS message when it has format: "RCS", or when it has rich_content or suggestions and no format. You don't need to set format when you send rich content, but RCS text with no suggestions needs format: "RCS".
A few things to know:
-
suggestions,rich_contentandfallback_messageonly work on RCS messages. Sending any of them withformat: "SMS"returns400. - The fallback is plain text only. It doesn't include suggestions or rich content, and there's no MMS fallback.
-
source_numberandsource_number_typeset the sender for the SMS fallback only. Withoutfallback_message, they aren't used. - Whether a recipient can receive RCS isn't known when you submit the message, so it never causes a request error. You'll see the outcome in the delivery report.
What do I need to do?
If you only send SMS or MMS, you don't need to do anything.
To start sending RCS through the API:
-
Get RCS enabled on your account. Contact your account manager. Until RCS is enabled, RCS requests are rejected with
402 Payment Required. -
Update your integration. Add
suggestionsorrich_contentas needed. RCS is chosen automatically when they're present, or you can setformattoRCS. The Send messages reference has request examples, limits and the full channel selection rules. -
Decide on fallback. Add
fallback_messageif you want an SMS sent when the recipient can't receive RCS. - Check your polling integrations (see below).
Before you start: polling
RCS delivery reports and free-text replies appear in your account's existing delivery reports and replies endpoints. Polling covers the whole account and can't be filtered per integration. So once anyone on your account sends RCS, every integration polling that account starts receiving RCS events.
Two things differ from SMS replies:
- A reply that comes back over RCS has its text in a
bodyarray instead ofcontent. This includes replies to upscaled messages when the reply comes back over RCS. Replies that come back as SMS are unchanged. - Suggestion taps only go to your reply webhook, with the suggestion's
postback_dataif you set one. They don't appear in the replies endpoint.
If more than one integration polls the same account, check they can handle RCS events before you start. We recommend webhooks for delivery reports and replies.
Frequently asked questions
Does this change my existing SMS integration?
No. SMS and MMS requests work exactly as they do today.
Which countries is this available in?
Every country where RCS is available on Sinch Engage. See RCS overview.
I already use RCS upscaling. Does anything change?
Upscaling of SMS sends carries on as it does today. If you poll for replies, note that a reply that comes back over RCS has its text in body instead of content (see "Before you start: polling"). Use format: "RCS" when you want suggestions or rich content, or want to choose the fallback text yourself.
Which suggestion types can I use?
Quick reply (reply), open a link (url), call a number (dial) and show a location (location). Other types, including calendar events, aren't supported and are rejected with 400.
How do I know when someone taps a suggestion?
Taps go to your reply webhook, including the suggestion's postback_data if you set one. They aren't returned by the replies endpoint, so you'll need a webhook to receive taps.
Can I combine text, suggestions and rich content in one message?
Not all of them. A message has either content (with optional suggestions) or one piece of rich content: an image or file, a card, a carousel or a location pin. Cards and carousels carry their own buttons. With format: "RCS", a request that combines them is rejected with 400.
What happens if my media URL doesn't work?
The file must be a type RCS supports, and its URL must be publicly reachable over http or https. We don't check the file's type or reachability when you submit the message, so any delivery problem shows in the delivery report.
What happens if one message in a batch is invalid?
As today, you can send up to 100 messages per request. If any message is invalid, the whole request is rejected and no messages are sent.
Developer documentation
- Send messages: RCS text, suggestions, images and files, fallback, limits and errors
- Get message status: RCS fields returned on status checks
- Check delivery reports and Check replies: polling endpoints