How to send a RCS Message - Sinch

This guide explains how to send RCS messages through Sinch using Batch’s Universal Channel feature.

By integrating Batch with Sinch, you can trigger RCS messages as part of your customer engagement strategy, leveraging Batch’s segmentation, automation, and orchestration capabilities.

This integration allows you to:

  • Send RCS messages via Sinch from Batch automations

  • Trigger messages based on user behavior or events

  • Centralize orchestration within Batch while relying on Sinch for delivery

circle-info

This integration uses Sinch’s Conversation APIarrow-up-right to manage and send RCS messages.

1

Step 1 — Configure Sinch

In your Sinch dashboard:

  1. Create a new RCS apparrow-up-right and enable it, or use an existing already enabled app.

  2. Retrieve your API credentials:

    • Key ID and Key secret

  3. Configure your RCS agentarrow-up-right (sender)

Make sure your Sinch setup allows sending messages to your target countries and users.

2

Step 2 — Add your Sinch API key into Batch

Batch needs your Sinch credentials to authenticate each time it sends a trigger request.

In Sinch

You can find all of your IDs and authentication credentials on the Sinch Customer Dashboardarrow-up-right.

In Batch

  1. Go to Settings → Channels → Universal

  2. Click New Credential Headers

  3. Choose a name (e.g., “Sinch”, "RCS",...)

  4. Key → Authorization

  5. Value → Basic [key ID]:[Key secret]→ encoded in base64 (e.g. Basic dFlPVVJfS0VZX0lEOllPVVJfS0VZX1NFQ1JFVA==)

  6. Save

Add the information in the Universal channel settings
Add the information in the Universal channel settings

Note: You only need to add the credential once in Batch.

3

Step 3 — Configure the Universal step in Batch

In this step, you will add the Universal step in your Batch automation and configure it to trigger the RCS messages.

Add the Universal Step

  1. Open the Batch automation where you want to trigger RCS

  2. Click the + button

  3. Select Universal

This opens the Universal step configuration screen.

Select "Universal"

Configure the Sinch request

Fill in the fields using the information from Sinch :

1. Destination URL

Paste the URL shown in Sinch’s API documentation (example: https://eu.conversation.api.sinch.com/v1/projects/b45375e2-4c0e-3b65-81b6-b256902c1dc9/messages:send )

3. Headers

  • Choose the credential header you created earlier (e.g., "RCS")

4. JSON Body

Example payload:

{
  "app_id": "<YOUR_APP_ID>",
  "recipient": {
    "identified_by": {
      "channel_identities": [
        {
          "channel": "RCS",
          "identity": "{{b.phone_number}}"
        }
      ]
    }
  },
  "message": {
    "text_message": {
      "text": "Hello {{ firstname }}, your order has been confirmed."
    }
  },
  "channel_priority_order": ["RCS"]
}
Configure the step
Configure the universal channel step
4

Step 4 — Test the connection

Once your Universal Step is configured, you can test it directly from Batch to make sure everything is working properly.

How to test

  1. In the Universal Step, click Test API.

  2. If your JSON body includes personalization (e.g., {{b.phone_number}}), choose a test profile so Batch can fill in real data.

  3. Click to send the test request.

Test your configuration
Use the "Test API" button in order to make sure everything is working properly

What the test does

  • Batch performs the exact same API call it will make when the automation is live.

What Batch validates

Batch will display whether the request was successfully delivered to Sinch or if something needs fixing (e.g., wrong URL, missing key, invalid JSON).

Note: Batch can only confirm that the trigger was correctly called. It does not have visibility on what happens inside Sinch afterward (e.g., whether the message was sent or failed).

5

Step 5 — Activate your Batch automation

When the test is successful, you can turn your Batch automation live.

To activate

  1. Review your workflow, including the Universal step.

  2. Run your automation

Once live

  • Every time a profile moves through this step in your automation, Batch will send the API request to Sinch.

Additional Universal steps

If you want to trigger multiple RCS scenarios (e.g., a follow-up message, or different RCS messages), you can add more Universal Steps within the same Batch automation or in a new one by following these steps again (Step 2 can be skipped).

Last updated