DEVELOPERS

RCS API: build verified RCS into your product

SimplyRCS publishes a REST API with 195 documented endpoints covering verified RCS sender IDs, blasts, bots, contacts, conversations, compliance, analytics and webhooks. The reference is public: no account, no sales call, no gated PDF. A scoped API key is required only to make live calls.

The API is included at the published rates: the same $0.0039 per text segment and $0.0150 per card or media message as the app, with no developer tier or per-call fee. See every rate.

curl -X POST https://api.simplyrcs.com/v1/messages/send \
  -H "Authorization: Bearer $SIMPLYRCS_API_KEY" \
  -H 'Idempotency-Key: order-48213' \
  -H 'Content-Type: application/json' \
  -d @message.json   # body: SendMessageRequest

import os, json, requests
r = requests.post("https://api.simplyrcs.com/v1/messages/send",
    headers={"Authorization": f"Bearer {os.environ['SIMPLYRCS_API_KEY']}",
             "Idempotency-Key": "order-48213"},
    json=json.load(open("message.json")))  # SendMessageRequest
print(r.status_code, r.json())

Read the API reference See pricing See published pricing

RCS Business Messaging API

One REST API sends RCS, SMS and MMS from the same verified sender, with the fallback chosen per recipient. A direct send is one call. messageType defaults to MARKETING, which applies the strictest consent gates; pass TRANSACTIONAL or OTP for the flows that are. An optional Idempotency-Key header makes a retry replay the original response for 24 hours instead of sending twice.

curl -X POST https://api.simplyrcs.com/v1/messages/send \
  -H "Authorization: Bearer $SIMPLYRCS_API_KEY" \
  -H 'Idempotency-Key: order-48213' \
  -H 'Content-Type: application/json' \
  -d '{ "messageType": "TRANSACTIONAL", ... }'   # fields: SendMessageRequest in the reference

# 200  Message accepted and dispatched      -> SendMessageResponse
# 409  Idempotency-Key reused with a different body

The full request and response schemas, every other endpoint and a sample in three languages are in the Conversations section of the API reference. For how the RCS API relates to Google’s RBM API underneath it, read the RCS API overview.

What you can build on one RCS and SMS API

Send verified, branded RCS

Register and manage verified RCS sender IDs, then send rich cards, carousels and suggested actions from your own code. Messages arrive under your brand name, logo and verification checkmark.

Fall back to SMS and MMS automatically

One send call reaches every recipient. Where RCS is not supported the same message is delivered as SMS or MMS, so you author once and each handset gets the richest format it can render.

Run blasts and bots programmatically

Create and schedule blasts, build bots, and drive two-way conversations, all through the same REST API rather than a console-only workflow.

Receive delivery and engagement events

Webhooks push delivery receipts, read receipts, button taps and inbound replies to your endpoint as they happen, so your CRM stays in sync without polling.

Register brands and campaigns for 10DLC

Compliance and vetting submissions are first-class API resources, so the registration work that usually happens over email can be automated.

Pull analytics

Query delivery, engagement and cost data directly instead of exporting spreadsheets from a dashboard.

The API by section

Each section links to its full reference, with parameters, responses and an example request for every endpoint.

Common (23)
Sender IDs (32)
Programs (5)
Blasts (15)
Bots (10)
Dictionaries (17)
Contacts (18)
Compliance (15)
Templates (1)
Conversations (10)
Analytics (19)
Webhooks (6)
API Keys (4)
Events (10)
Submissions (7)
MCP (3)

Developer questions

Is SimplyRCS an SMS API provider as well as an RCS API for developers?

Yes. The same REST endpoint sends RCS, SMS and MMS from one verified sender, with the fallback chosen per recipient, so it works as an SMS API for business texting on its own and as an RCS API for developers who want rich cards, carousels and buttons without a second integration. The API is priced the same as the app.

Does SimplyRCS have an API?

Yes. SimplyRCS publishes a REST API with 195 documented endpoints across 16 sections, described by an OpenAPI 3.1 specification. The full reference is public and readable without an account.

Do I need an account to read the SimplyRCS API docs?

No. The reference is deliberately public so integration teams can evaluate the API and start building before production launch. A scoped API key is needed only to make live calls.

Is there an MCP server for SimplyRCS?

Yes. SimplyRCS exposes MCP endpoints so AI agents and assistants can work with the messaging platform directly. They are documented in the MCP section of the API reference.

What does the SimplyRCS API cost to use?

The API itself carries no platform fee. You pay usage-based US messaging rates with no monthly agent fee, and carrier, registry and vetting fees are passed through at cost. Full rates are published on the pricing page.

Can I migrate to SimplyRCS from another provider without downtime?

Yes. Numbers can be ported and 10DLC registrations moved with no overlap gap, and the API can run alongside your existing provider during cutover so traffic shifts gradually rather than all at once.

How the RCS API works, in plain English Webhook guide: delivery and engagement events All the ways to connect SimplyRCS SimplyRCS vs Twilio for developers