In short
- Send RCS to one or more numbers in international format (E.164, no
+) - Choose the type:
basic,card,carousel,file, ortemplate - (Optional) Pass
fromto send via branded agent - Query a send by the id returned in the response
- Cancel only while
QUEUEDorSCHEDULED
Before you start
- Key with
rcs:send(andrcs:read/rcs:cancelto query or cancel) - Numbers in E.164 (e.g.
5511999999999, no+) - Auth:
Authorization: Bearer sk_live_...orx-api-key - Base URL:
https://api.notifique.dev
1. Send RCS (text)
to is always an array (up to 500 recipients). One message is created per number.
messageIds to query or cancel.
Scope: rcs:send.
2. Other send types
On the API reference (RCS tab), open Send RCS and pick an example in the playground. Summary:CARD (one card)
On CARD, use
cardMessage for text. The message field is not shown to the recipient.CAROUSEL (three cards)
FILE
Workspace template
With branded agent (from)
type: basic, card, carousel, file, or template. messageType is accepted as a legacy alias.
Schedule: include "schedule": { "sendAt": "2026-12-31T14:00:00.000Z" } (plan-dependent).
In options: priority, webhook (url + secret) for this send only, metadata.
3. List history
status (comma-separated), to, fromDate, toDate. Scope: rcs:read.
4. Query status and sent content
SendPOST only returns messageIds and status (202). To see what was sent (payload, messageType, refer), query by id:
GET /v1/rcs/messages) also includes payload on each item. Scope: rcs:read.
5. List inbound replies
relatedRcsLogId). Detail: GET /v1/rcs/inbound/:id — relatedRcsLog has the same detail level as GET /v1/rcs/messages/:id (rcsId, messageType, payload, status, and delivery timestamps).
6. Cancel
Only with statusQUEUED or SCHEDULED:
rcs:cancel.
7. Avoid duplicates
Idempotency-Key header on send POST. Repeats within 24 h do not create duplicate sends. See Security and reliability.
8. Webhooks (optional)
Configurercs.sent, rcs.delivered, rcs.clicked, rcs.failed, and rcs.cancelled to track without polling.
Guide: Webhook events.
Next steps
- Introduction: when to use and message types
- RCS instances: branded agent
- Scopes: key permissions
- Webhook events: real-time status
- Error responses: HTTP codes and
code

