RCS API for Developers | SendRCSMessages

Platform · API

RCS API for developers

Q: What authentication does the API use?

API authentication method should be confirmed during integration; common approaches include API keys or bearer tokens.

Trigger branded RCS messages from your own systems, and receive delivery, read and reply events back — built to plug into your CRM, app or e-commerce platform.

What does the RCS API do?

The RCS API lets your own systems send branded RCS messages — rich cards, carousels and plain text — and receive delivery, read and reply events through webhooks, with SMS fallback where configured.

Talk to us about integration WhatsApp us

Illustrative

// Send a rich card — illustrative example
POST /v1/messages
Authorization: Bearer YOUR_API_KEY

{
  "to": "+9198XXXXXX12",
  "type": "rich_card",
  "title": "Monsoon Sale is live",
  "description": "Flat 30% off today",
  "image": "https://.../banner.jpg",
  "buttons": [
    { "label": "Shop now", "url": "https://yourstore.in/sale" }
  ],
  "fallback": "sms"
}

How it fits together

From your system to the customer's phone

Your systemCRM, app, e-commerce

→

SendRCSMessages APIValidates & routes

→

RCS infrastructureJio & carriers

→

Customer's phoneMessages app

Illustrative

// Example response
{
  "message_id": "rcs_8f2a1c",
  "status": "accepted",
  "channel": "rcs"
}

Endpoint names, fields and responses above are illustrative. Exact API specification, authentication method and base URL are confirmed during integration.

Webhooks

Events sent back to your system

message.deliveredThe message reached the supported recipient environment.

message.readA read event was received, where supported by the client.

message.failedDelivery could not be completed through the selected route.

message.replyThe customer replied with text, a suggested reply or postback.

button.clickedThe customer tapped a button or suggested action.

fallback.sentThe message was delivered as SMS fallback, where configured.

Webhook payloads should be authenticated or verified before being processed by your system.

Built for integration

What developers need to know

Authentication

API key or bearer token-based authentication — confirmed during integration.

Webhook verification

Verify incoming webhook payloads before processing them.

Rate limits

Limits depend on your plan and volume — confirmed during onboarding.

Sandbox / test mode

A test environment may be available — confirm for your account.

SMS fallback

Set a fallback channel per message, where configured.

Error handling

Clear error codes and statuses for failed or rejected requests.

Why integrate

Trigger RCS the moment something happens

Order placed, cart abandoned, appointment booked — fire a branded RCS message straight from your own systems, instead of a manual export.

Real-time triggers

Send the moment an event happens in your system.

No manual exports

Skip CSV uploads — connect directly to your data.

Events back to you

Delivery, read and reply data flows back automatically.

Reach preserved

SMS fallback where configured, so messages still land.

FAQ

API, answered

Does SendRCSMessages provide an API?

Yes. A REST API is available to trigger branded RCS messages from your own systems, with delivery and reply events available via webhooks, where supported by your setup.

What authentication does the API use?

The authentication method should be confirmed during integration; common approaches include API keys or bearer tokens.

Are there rate limits on the API?

Rate limits depend on your plan and volume and should be confirmed during onboarding.

Can I test the API before going live?

A sandbox or test environment may be available; availability should be confirmed for your account.

Back to Platform overview See analytics & reporting

Get started

Ready to integrate?

Talk to our team about your systems and use case.

Talk to us WhatsApp us