Pinnacle

Receiving RCS Messages

Receiving your first RCS message with Pinnacle's Typescript SDK

Prerequisites

Before proceeding, ensure you have obtained an RCS sandbox agent and API key as described in the prerequisites.

Installation

Initialize a new Node.js project:

Shell
npm init -y

Install the Pinnacle TypeScript SDK, Express, and dotenv:

Shell
npm install rcs-js@2.0.25 express dotenv

Install development dependencies:

Shell
npm install --save-dev @types/express @types/node tsx

This guide uses version rcs-js 2.0.25. It's compatible with the following runtimes: Node.js 18+, Vercel, Cloudflare Workers, Deno v1.25+, Bun 1.0+, and React Native.

Configuration

Create an .env file in your project root and add your Pinnacle API key and signing secret:

Shell
PINNACLE_API_KEY="your_api_key" # pnclk_
AGENT_ID="your_agent_id" # agent_
PINNACLE_SIGNING_SECRET="your_signing_secret" # pss_

Setting Up a Webhook

To receive inbound RCS messages, you need to configure a webhook in the Pinnacle dashboard:

  1. Navigate to Development > Webhooks in the Pinnacle dashboard
  2. Click Create new webhook
  3. Give your webhook a descriptive name
  4. Enter your webhook endpoint URL
    • For local development, use an ngrok tunnel pointing to localhost:3000/inbound-rcs
    • For production, use your deployed server URL
  5. After creation, copy the signing secret and add it to your .env file
  6. Add your RCS sandbox agent to your webhook for it to receive messages. You must also whitelist the devices you want to test with by navigating to your sandbox agent and adding test device phone numbers.

Optionally, you can configure custom HTTP headers (e.g. X-API-KEY) to be sent on every webhook delivery. Add them in the dashboard or via the headers field on POST /webhooks/attach. The PINNACLE-SIGNING-SECRET header is reserved.

Creating Your Webhook Endpoint

Create a new TypeScript file (e.g., index.ts) and use the complete example.

The complete example creates an Express endpoint that:

  • Receives webhook POST requests at /inbound-rcs
  • Verifies the webhook signature using your signing secret
  • Processes incoming message events and replies to a button press by the user

Running Your Server

Start the Express server:

Shell
npx tsx index.ts

Your server will start on http://localhost:3000. If you're using ngrok for local development, start it in a separate terminal:

Shell
ngrok http 3000

Use the ngrok URL (e.g., https://abc123.ngrok.io/inbound-rcs) as your webhook endpoint in the Pinnacle dashboard.

Testing Your Webhook

Send a POST request using your whitelisted test number. This unauthenticated demo endpoint is for local testing only.

Shell
curl -X POST "http://localhost:3000/send-rcs/+14155550123"

If there are no errors, you should see something like

JSON
{
  "message_ids": null,
  "segments": 1,
  "total_cost": 0.03,
  "sender": "agent_exampleId",
  "recipient": "+12345678910",
  "status": "queued",
  "messageId": 6828
}

and receive a message on your whitelisted device like this: rcs message

If you're not receiving any messages, make sure you have

  • Your RCS sandbox agent associated with your webhook
  • Your test device is whitelisted

If you tap "Say hello back", your whitelisted device should receive a text saying "Hello! Button clicked successfully."

With that, your webhook should now be successfully receiving inbound RCS messages as well message status updates for outbound messages! You can monitor these statuses by filtering events by their message direction set to outbound:

TypeScript
if (event.type === "MESSAGE.RECEIVED" && event.direction === "OUTBOUND") {
  console.log(event);
}

For more detail about processing the message payload received, please view the process method.

Pinnacle referenceAsk Pinnacle

Get a sourced answer from the published documentation.

ViewingPinnacle documentation

Conversations are saved for analysis.

Try asking