REST API integration, webhook-based workflows, and implementation guidance for RCS Business Messaging. MetaReach RCS is priced from ₹0.50 down to ₹0.30 per message by monthly volume, plus GST.
MetaReach's RCS API is a REST interface for sending rich cards, carousels, and suggested replies programmatically from your own app or CRM, with webhook callbacks for supported delivery and read status events. The setup and pricing vary by implementation requirements, message format, and campaign scope. MetaReach RCS is priced from ₹0.50 down to ₹0.30 per message by monthly volume, plus GST.
Put simply, the RCS API is a REST interface that lets your own application send Rich Communication Services messages — rich cards, image carousels, suggested replies, the works, where supported — without anyone touching a dashboard. Instead of logging in to send a campaign one batch at a time, you trigger the message from inside a workflow: an order confirmation the second a payment clears, a delivery update the moment a shipment status changes, or a personalised offer fired off by something a user just did on your site.
It sits inside MetaReach's RCS Messaging (see RCS overview) platform and can be approached much like our SMS API and WhatsApp Business API — so if your team has already worked with either of those, your existing API experience may help streamline RCS integration.
Your system sends an HTTP request to the configured endpoint with recipient and message details. Carrier routing, recipient eligibility, fallback behaviour, and delivery-status callbacks depend on the selected platform, provider, and integration. SMS fallback may be configured for eligible workflows where supported; delivery remains subject to configuration and network conditions.
Requests are typically authenticated with credentials such as an API key, passed as a header on each call. The example below is illustrative only — the actual host, endpoint path and authentication method are confirmed during onboarding for your setup:
Here's a basic rich-card send, stripped down to the essentials:
This is illustrative. Detailed request/response specifications depend on the available implementation and documentation for your setup.
Many teams hook the RCS API into their CRM so messages fire directly off customer records — a rich-card appointment reminder the moment a lead's status changes, say, or a carousel of recommended products pulled from someone's purchase history. Supported delivery/read status events may be synced back through configured webhooks, so sales and support can see message status without leaving the tool they already live in.
Where supported, you can register a webhook_url for status callbacks.
Supported webhook events may provide delivery, read, or failure status depending on
platform/provider/configuration. That lets your system learn about status changes as they
are reported, instead of asking the API repeatedly and using up quota unnecessarily.
API responses may include status codes and error details according to the implementation. Authentication failures, malformed payloads, and invalid recipient numbers are typically rejected at the API level. Delivery-side failures (device unreachable, message expired) may surface later as a webhook event, not as an error on the original API call, since the send itself can succeed even if delivery hasn't happened yet.
Exact status codes and error payloads depend on the documentation available for your setup — this is the general shape so you can design your retry logic early.
API access, implementation support, and documentation needs vary by deployment. MetaReach RCS is priced from ₹0.50 down to ₹0.30 per message by monthly volume, plus GST. Contact us for a recommended setup based on your use case and expected volume. See the RCS Pricing India 2026 page for general pricing considerations.
It's a REST-based interface for sending RCS Business Messages — such as rich cards, carousels and suggested replies where supported — from your own application, CRM, or backend, instead of a dashboard. It's built for developers and businesses wiring RCS into an automated workflow.
Sandbox access and testing requirements depend on the implementation. Contact MetaReach to discuss the available environment for your use case.
Webhook events and timing depend on the platform, provider, and integration configuration. Confirm supported event types and delivery behaviour for your setup.
RCS API pricing depends on message volume, format, and integration requirements. MetaReach RCS is priced from ₹0.50 down to ₹0.30 per message by monthly volume, plus GST. Contact us for implementation guidance.
CRM integration depends on your CRM, provider and configuration. Where supported, messages can be triggered from customer records, supported delivery and read status events can be synced back through configured webhooks, and messaging can be automated around lead or order status changes.
From startups to enterprises — brands that grow with MetaReach
Guides, comparisons, pricing & city coverage — everything about RCS business messaging in India
Ready to launch your first RCS campaign? MetaReach handles setup end to end — go-live timing depends on brand/agent approval, carrier readiness and your creative or API setup.
