RCS via REST API

Send a POST request to https://api.sendrcs.eu/api/rcs/send with your API key in the X-API-Key header and a JSON body containing the sender ID, the recipient and the message content - for example a Rich Card with title, description, image and a button. The response returns a message ID and status. Full examples for every format are in the API documentation.

Every request needs an API key in the X-API-Key header. You generate and manage your keys in the SendRCS dashboard under Settings and API Keys.

Nine formats: Basic Text (up to 160 characters), Rich Text (up to 3,072 characters and 11 suggestion chips), Rich Card, Carousel (up to 10 cards), image, video, audio, file (PDFs and documents) and generic media with suggestion chips. Seven button types are available: postback, openUrl, openUrlInWebview, dial, createCalendarEvent, viewLocation and shareLocation.

Yes. The batch endpoint sends the same message to up to 10,000 recipients in a single API call. Deactivated contacts are filtered automatically, batch size and delay are configurable, and a campaign name lets you track and report on the send.

Define an SMS fallback text for each message. The API detects automatically whether the recipient can receive RCS and otherwise sends the SMS instead, with a separately configurable SMS sender and up to 1,530 characters of text. The API response tells you when and why a fallback was used.

Yes. Pass a scheduleAt time with IANA timezone support, such as Europe/London, and the message is sent at that moment in the recipient's local time. You can validate a time in advance via the validate-schedule-time endpoint and cancel a scheduled job with DELETE /batch/{jobId}.

Via webhooks. SendRCS calls your backend in real time for six events: button clicks with your custom postbackData, delivery status changes (delivered, read, failed), incoming RCS messages, incoming SMS to your virtual numbers, form submissions and confirmed double opt-ins. Button webhook URLs are set per button, the others under Settings and Webhooks in the dashboard.

Yes. The public sandbox at https://api.sendrcs.eu/api/rcs/sandbox/preview validates any message body with the same rules as the real send endpoint and returns a share link that renders the message on an Android and iOS phone mockup. No API key is needed, nothing is sent and no credits are used. The link expires after 24 hours, and the rate limit is 20 requests per minute and 100 per day per IP.

Yes. The same API key gives you a standalone SMS endpoint, the message log and full CRUD endpoints for contacts, custom fields, groups and message templates under https://api.sendrcs.eu/api/v1/. Message text supports merge fields such as {{contact_first_name}} and a unique per-recipient {{unsubscribe_link}}.

Because iPhones reject text and textBasic messages whose text contains an email address or a web address (URL, www. host or bare domain), while Android delivers them. The message is still accepted; the /validate endpoint and the sandbox return a warning so you can decide. To reach every phone, put links on chips and buttons, or use a rich card: card titles, descriptions and chip labels may contain an address.