Send RCS Message | Pinnacle

Send a RCS message immediately or schedule it for future delivery.

Requires an active RCS agent and recipient devices that support RCS Business Messaging.

Authentication

PINNACLE-API-KEYstring

API Key authentication via header

Request

This endpoint expects an object.

TextobjectRequired

Send a text RCS message with optional quick reply buttons.

MediaobjectRequired

Send a media RCS message with optional quick reply buttons.

CardsobjectRequired

Send a cards RCS message with quick replies / buttons.

Quick replies are shared across all cards in the carousel
While buttons resemble quick replies, they remain on screen after being clicked and are card-specific.

Send a cards RCS message with quick replies / buttons. - [Quick replies](/api-reference/messages/send-rcs#request.body.Cards.quickReplies) are shared across all cards in the carousel - While [buttons](/api-reference/messages/send-rcs#request.body.Cards.cards.buttons) resemble quick replies, they remain on screen after being clicked and are card-specific.

Response

Successfully sent or scheduled the message.

Use our /messages/:id endpoint to track your message.

About RCS Fallback SMS Response and RCS Fallback MMS Response

Normally, when you send an RCS message with a fallback, the RCS message is attempted first — if delivery fails, the fallback SMS or MMS is sent afterward and you receive a FALLBACK_SENT webhook event.

These response types are part of our new rollout that detects whether a recipient’s phone is RCS-capable before the message is sent. If the phone does not support RCS, the fallback SMS or MMS is sent immediately — skipping the failed RCS attempt entirely. They can be ignored unless you have been specifically onboarded to use them. If you’re interested, contact us at founders@trypinnacle.app.

When you receive one of these responses, you will not receive a FALLBACK_SENT webhook event — the fallback was already sent in place of the RCS message.

Successfully sent or scheduled the message. Use our [/messages/:id](./get) endpoint to track your message. <Accordion title="About RCS Fallback SMS Response and RCS Fallback MMS Response"> Normally, when you send an RCS message with a fallback, the RCS message is attempted first — if delivery fails, the fallback SMS or MMS is sent afterward and you receive a `FALLBACK_SENT` webhook event. These response types are part of our new rollout that detects whether a recipient's phone is RCS-capable **before** the message is sent. If the phone does not support RCS, the fallback SMS or MMS is sent immediately — skipping the failed RCS attempt entirely. They can be ignored unless you have been specifically onboarded to use them. If you're interested, contact us at founders@trypinnacle.app. When you receive one of these responses, you will **not** receive a `FALLBACK_SENT` webhook event — the fallback was already sent in place of the RCS message. </Accordion>

RCS Sent Responseobject

Scheduled Responseobject

RCS Fallback SMS Responseobject

RCS Fallback MMS Responseobject

Errors

Successfully sent or scheduled the message.

Use our /messages/:id endpoint to track your message.

About RCS Fallback SMS Response and RCS Fallback MMS Response

When you receive one of these responses, you will not receive a FALLBACK_SENT webhook event — the fallback was already sent in place of the RCS message.

1	import { PinnacleClient } from "rcs-js";
2
3	const client = new PinnacleClient({ apiKey: "YOUR_API_KEY" });
4	await client.messages.rcs.send({
5	quickReplies: [{
6	type: "openUrl",
7	payload: "payload",
8	title: "title"
9	}],
10	text: "text",
11	from: "from",
12	to: "to"
13	});

1	{
2	"messageId": "msg_1234567890",
3	"segments": 1,
4	"totalCost": 0.03,
5	"sender": "agent_pinnacle",
6	"recipient": "+14154746461",
7	"status": "queued"
8	}