Skip to main content
RCS is SMS with superpowers: when the device and carrier support it, you send images, buttons, and carousels, still to a phone number.

​
What is RCS on Notifique?

It’s the channel for rich mobile messages (Rich Communication Services). The destination is still an international phone number (E.164, no +), like SMS, but content can go beyond plain text. You can:
  • Send text (BASIC), image cards with buttons (CARD), carousels (CAROUSEL), or files via URL (FILE)
  • Dispatch to 1 to 100 numbers per call (one message per number)
  • Schedule sends for a future date and time
  • Query status of each send by id
  • Cancel while queued or scheduled
  • Track short-link or button clicks via webhook
Think of a digital flyer in the pocket: more visual than SMS, but only reaches devices on RCS-capable networks.
Unlike WhatsApp, RCS does not use a channel instance. You only need an API Key with the right scopes and numbers in international format (e.g. 5511999999999).

​
When to use it?

Works great for campaigns with images and buttons, promotional alerts, and better conversion than plain SMS, for RCS-capable recipients. For OTP that must reach any phone, prefer SMS. Not every device delivers RCS; have a plan B (SMS, WhatsApp, or email) when delivery must be guaranteed.

​
Message types

  • BASIC, text only
  • CARD, image, title, description, and buttons
  • CAROUSEL, multiple cards in one message
  • FILE, file via public URL + filename
Field details per type: API reference on the RCS tab.

​
How it works in practice

  1. Create an API Key with rcs:send (and rcs:read / rcs:cancel to query or cancel)
  2. Send with POST /v1/rcs/messages, to as an array, type and payload per format
  3. The platform queues, sends, and updates status; your backend gets alerts if you configured webhooks
Each API Key belongs to one workspace. On v1 do not send x-workspace-id.

​
Message lifecycle

After send, RCS moves through statuses like QUEUED, SCHEDULED, PROCESSING, SENT, DELIVERED, CLICKED, FAILED, or CANCELLED. API cancellation works while status is QUEUED or SCHEDULED. With short links enabled, the first click on a clicar.co link from the send may mark CLICKED, webhook rcs.clicked.

​
What you can do

  • Send to 1 to 100 numbers per call (60 credits per message)
  • Schedule with schedule.sendAt
  • Query one send by returned id
  • Cancel while queued or scheduled
  • Idempotency with Idempotency-Key header
  • Per-send webhook in options.webhook (that batch only)
See Billing. Error details: API reference on the RCS tab.

​
After your first send

  • Track delivery, clicks, and failures via webhooks (rcs.sent, rcs.delivered, rcs.clicked, rcs.failed)
  • Handle FAILED with SMS or another channel when the network does not deliver RCS
  • Test in Sandbox with sk_test_... before production

​
Next steps