Skip to content

Adding the Sinch Channel

Virtual Assistants built on the XO Platform can be deployed on the Sinch Conversation API platform.

The Sinch Conversation API allows developers to create robust omnichannel messaging experiences across multiple interaction channels.

Why Sinch Conversation API?

  • Provides support for message sending, conversation management, user authentication, and rich message formatting, empowering developers to deliver seamless and engaging user communication experiences.
  • Offers built-in transcoding for smooth conversations across all supported channels, with optional full control over channel-specific features.
  • Consolidates all conversation details into a single callback, streamlining integration with the XO Platform.

Prerequisites

  • Access to the XO Platform Bot Builder. Learn more.
  • A working virtual assistant on the XO Platform to test the channel enablement. Learn more.
  • Enabling the Sinch Conversation API requires signing up on the Sinch developer dashboard.

To set up the channel, you must associate the VA with a Sinch app and set up the required delivery channel. The steps to complete the channel enablement are summarized below:

  1. Capture the Sinch Project Access keys for Authentication.
  2. Create an App.
  3. Configure the Webhook URL.
  4. Configure the delivery channel.
  5. Enable the Channel on the XO Platform.

Step 1: Capture the Sinch Project Access keys for Authentication

Once you create an account and log in, accept the terms and conditions and create your access key.

The Conversation API uses OAuth2 tokens for authentication, which can be obtained from an OAuth2 token endpoint. To authenticate, a client_id (or KEY ID) and client_secret (or KEY SECRET) are used. You can generate new Access Keys, each with a new KEY ID and KEY SECRET, at any time.

To create an access key, follow the steps below:

  1. Log in to your Sinch account and navigate to the developer dashboard.
  2. Select Settings in the left menu and navigate to the General Settings screen.
  3. Select Access Keys under Settings and navigate to the Access Keys screen. access keys

    This page shows your project(s) and corresponding Project ID(s) and a list of your Access keys and the corresponding KEY IDs.

  1. In the top left corner of your screen, next to the Sinch logo, select the desired project from the Project dropdown.
  2. Copy and save the Project ID of your project. Paste it into the relevant field on the XO Platform’s Sinch Configurations page. Learn more.
  3. copy project id

You can also copy the Project ID by clicking Conversation API > Overview on the left menu.

conversation api

Note

When you sign up for a Sinch account, a default project is created for you. Conversation API uses this project to group contacts and apps together. To create additional projects, contact your Sinch account manager for assistance.

  1. Click the New Key or Create Access Key button in the Access Keys List section.
  2. Provide a display name for your access key in the New Access Key window, and click Confirm. new access key
  3. The Key is created, and the Key ID & Key Secret are generated as shown in the form below. key id and secret
  1. Copy the Key ID and Key Secret and paste them into the relevant field on the XO Platform’s Sinch Configurations page. Learn more.

Important

You must copy and store the generated Key Secret. You cannot retrieve it again once you’ve created the key.

  1. Click Confirm.

You are returned to the Access Keys page, where your new key is displayed in the Access key list section.

Note

The KEY SECRET is only displayed when a new Access key is created.

Step 2: Create An App

The next step is to create and configure a Conversation API app to enable the channel.

Follow the steps below to create an app. Alternatively, you can use API calls to create an app.

  1. Select Conversation API > Apps on the left menu.
  2. On the Conversation Apps page, click the NewApp button in the Apps section.

    conversation apps

  3. In the New App form. Provide the app’s Display Name and select the region from the dropdown menu.

Note

  • The region you select determines where your Conversation API app is hosted and where its associated data is stored. Once a region is chosen for your app, it cannot be changed.
  • Based on the region selected, capture the Sinch region Base URL and provide it in the configuration tab of this page. See the list of Sinch region URLs.

new app

  1. Click Create. The newly created APP is displayed in the Apps section. new app id
  2. Click the App Name and go to the App Details screen.
  3. Copy and save the App ID displayed in the Configuration section. Paste it into the relevant field on the XO Platform’s Sinch Configurations page. Learn more.
  4. copy and save app id

Step 3: Configure the Webhook URL

To send and receive messages, you need to configure at least one channel using a webhook URL for your app. To configure, follow the steps below:

  1. Select the App created by you on the Apps page.
  2. Scroll down to the Webhooks section and click Add Webhook. add webhook

The New webhook form is displayed.

new webhook form

  1. In the Target type dropdown, select HTTP.
  2. In the Target URL field, copy and paste the WebHook URL value from the XO Platform’s Channels > Sinch > Configurations section. Learn more.
  3. In the Secret token field, copy and paste the value for Verify Token from the XO Platform’s Channels > Sinch > Configurations section. This token enables the webhook to validate against your chosen endpoint.
  4. configure on xo
  1. In the Triggers dropdown, select all the triggers you want to add to the webhook.
  2. Click Create.
  3. click create webhook

The webhook is created and displayed in the Webhooks section of the app page.

webhook listing

Step 4: Configure the Delivery Channel

Next, you must configure the delivery channel for the conversations with the steps given below:

  1. Select the app you’ve created on the Apps page.
  2. Scroll down to the Setup Channels section.

    set up channels

  3. Select the delivery channel you want to configure.

  4. To set up the required channel, click the channel listing here.

Step 5: Enable the Channel on the XO Platform

To enable the channel on the UXO Platform, follow the steps below:

  1. Go to Automation AI > Flows & Channels on the left navigation menu.
  2. Select Digital under Channels.
  3. Click the All tab, and select Sinch in the Enterprise Channels section.
  4. select Sinch
  1. Click the Configurations tab.
  2. Copy the relevant field values from your Sinch Conversation API app and paste them into the relevant fields as follows:
  • Sinch Region Base URL: Copied in Step 3 here.

  • Project ID: Copied in Step 5 here.

  • Access Key Id and Access Key Secret: Copied in Step 8 here.

  • App ID: Copied in Step 6 here.

  1. Select 'Yes’ for Enable Channel.
  2. Click Save.
  3. xo platform sinch configurations

After enabling the channel and verifying all the configurations, you can test the new channel integration by publishing your virtual assistant. Learn more.

Message Types

Conversation API uses generic message types to send the same message to multiple channels. In cases where the channel doesn’t natively support the message type, the message will be transcoded. The supported message types include:

Message Templates

Sinch message templates are predefined, structured formats for sending recurring or standardized messages across channels like WhatsApp, SMS, and other supported platforms.

These templates ensure compliance with the channel’s messaging policies, especially for platforms like WhatsApp that require pre-approved templates for certain messages, such as notifications or service updates. Message templates can be used during virtual assistant conversations to structure the messages. The default template types include:

For additional assistance with using Message Templates and Types for your Sinch channel on the UXO Platform, please contact our developer support team.

To learn more about working with messaging channels within the UXO Platform, please see Channel Enablement.