Send rich cards, carousels, and text messages programmatically. REST endpoints, webhook-based delivery and read-receipt tracking, and automatic SMS fallback- built for CRM and app integration.
Node.js, Python, PHP, and Java SDKs available
Trusted by 10,000+ businesses across India
The RCS API is Get Click Media's REST interface for sending RCS Business Messages programmatically- rich cards, carousels, suggested-reply, and plain text messages- straight from your own app or CRM. Every request is authenticated with a bearer-token API key, and webhooks report delivery status and read receipts back to your systems in real time instead of requiring you to poll for updates.
Businesses use the API to trigger RCS sends directly from the systems they already run- an order confirmation, an OTP, or a campaign- without building a separate messaging tool. Messages that can't reach a recipient as RCS fall back to plain SMS automatically, so an integration built once keeps working regardless of which devices are on the other end.
Every request is authenticated with an API key issued when your account is provisioned, passed as a bearer token in the request header.
Authorization: Bearer YOUR_API_KEY
Content-Type: application/jsonIllustrative request format- your onboarding contact confirms exact field names and base URL for your account before you go live.
curl -X POST https://api.getclickmedia.com/v1/rcs/messages \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+9198XXXXXXXX",
"type": "rich_card",
"richCard": {
"title": "Flash Sale- 30% Off",
"imageUrl": "https://cdn.example.com/sale-banner.jpg",
"description": "Today only. Tap below to shop the sale.",
"actions": [
{ "type": "openUrl", "label": "Shop Now", "url": "https://example.com/sale" }
]
}
}'curl -X POST https://api.getclickmedia.com/v1/rcs/messages \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+9198XXXXXXXX",
"type": "carousel",
"cards": [
{ "title": "Product A", "imageUrl": "https://cdn.example.com/a.jpg",
"actions": [{ "type": "openUrl", "label": "View", "url": "https://example.com/a" }] },
{ "title": "Product B", "imageUrl": "https://cdn.example.com/b.jpg",
"actions": [{ "type": "openUrl", "label": "View", "url": "https://example.com/b" }] }
]
}'Register a webhook URL to receive real-time delivery-status and read-receipt events, instead of polling the API for status updates.
{
"event": "message.delivered",
"messageId": "msg_9f2a1c",
"to": "+9198XXXXXXXX",
"status": "delivered",
"channel": "rcs",
"timestamp": "2026-07-01T10:15:00Z"
}Fires when a message is sent, delivered, falls back to SMS, or fails- with a timestamp and reason.
Fires when the recipient opens the message inside Google Messages, for engagement tracking.
In addition to webhooks, you can poll message status directly by ID- useful for reconciliation jobs and dashboards.
| Endpoint | Purpose |
|---|---|
| POST /v1/rcs/messages | Send a message (text / rich card / carousel) |
| GET /v1/rcs/messages/{id} | Check delivery status of a sent message |
| POST /v1/rcs/webhooks | Register a delivery-status or read-receipt webhook |
POST /v1/rcs/messages
GET /v1/rcs/messages/{id}
POST /v1/rcs/webhooks
Keep your API key server-side only- never ship it in client-side/mobile app code.
Check the delivery-status webhook for a fallback event so your app can log or route it correctly.
Register delivery and read-receipt webhooks instead of repeatedly polling the message-status endpoint.
Malformed rich-card or carousel JSON is the most common cause of send failures- validate structure client-side first.
Batch sends and back off on 429 responses rather than retrying immediately in a tight loop.
A 200 response means the request was accepted- track the delivery webhook to confirm the message actually reached the device.
Get Click Media enables developers to send rich cards, carousels, and track delivery programmatically with RCS.
Big or small, we power communication for all- talk to us today.
Yes- a REST API for sending rich cards, carousels, and text messages, with webhook support for delivery and read-receipt status.
Authentication uses an API key issued during onboarding, passed as a bearer token in the Authorization header of every request.
Text, rich cards, carousels, and suggested-reply / suggested-action messages are all supported.
Yes- webhooks are available for delivery status and read receipts, so you can track engagement in real time instead of polling.
Ask your onboarding contact about sandbox/test-mode access for your account- availability can depend on your plan.
Messages automatically fall back to SMS when RCS delivery isn't available on the recipient's device or network, so no message is lost.
Yes- the REST API integrates with common CRMs and e-commerce platforms via standard HTTP calls, the same way our WhatsApp and SMS APIs do.
Rate limits apply and vary by plan- your onboarding contact will confirm the exact tier for your account so you can design your integration accordingly.
Errors typically relate to invalid recipient formatting, an unverified sender ID, or rich-card/carousel payload validation failures. Full error-code documentation is provided during API onboarding.
Yes- illustrative REST examples for sending rich cards and carousels are shown below, and full documentation with tested samples is provided once your API key is issued.
Talk to our integration team for API access, full endpoint documentation, and SDK support.
