DocumentationJourney OptimizerJourney Optimizer Guide

Configure Sinch provider sms-configuration-sinch

Last update: May 20, 2026

CREATED FOR:

  • Intermediate
  • Admin

When using the Sinch provider with Journey Optimizer, you can find three distinct options:

  • SMS Configuration: Set up your Sinch API credentials to send SMS messages seamlessly.

  • MMS Configuration: For multimedia messaging (MMS), configure your Sinch MMS API credentials. Note that tracking and responding to inbound messages, are handled by the SMS configuration. MMS setup is only for outbound delivery of the MMS message.

  • RCS Configuration: Set up your Sinch API credentials to send RCS messages seamlessly.

To configure your Sinch provider, follow the steps below:

  1. Create API Credential
  2. Create Webhook
  3. Create Channel configuration
  4. Create Journey or Campaign with SMS channel action

Configure API credentials for SMS create-api

To configure your Sinch provider to send SMS messages and MMS with Journey Optimizer, follow these steps:

  1. In the left rail, browse to Administration > Channels > SMS Settings and select the API Credentials menu. Click the Create new API credentials button.

  2. Configure your SMS API credentials, as detailed below:

    accordion
    List of SMS credentials for configuration
    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2
    Configuration fields Description
    SMS vendor Sinch
    Name Choose a name for your API Credential.
    Service ID and API Token Access the APIs page, you can find your credentials under the SMS tab. Learn more in Sinch Documentation.
    Inbound Number Add your unique inbound number or short code. This allows you to use the same API credentials across different sandboxes, each with its own inbound number or short code.
    Override URL Enter your custom URL to replace the default endpoints for SMS delivery reports, feedback data, inbound messages or event notifications. Sinch will send all relevant updates to this URL instead of the predefined ones.

  1. Select Use custom dataset for inbound to route this credential’s inbound SMS to a pre-created dataset you choose from the dropdown. Learn more about using a custom dataset for inbound keywords

    note
    NOTE
    The dataset schema must be XDM ExperienceEvent and include at least these field groups:
    • Adobe CJM ExperienceEvent - Message interaction details
    • Adobe CJM ExperienceEvent - Message Execution Details
    • Adobe CJM ExperienceEvent - Message Profile Details
    The schema and dataset must be enabled for Profile.

  2. Click Submit when you finished the configuration of your API credentials.

  3. In the API Credentials menu, click the bin icon to delete your API credentials.

  4. To modify existing credentials, locate the desired API credentials and click the Edit option to make the necessary changes.

  5. Click Verify SMS connection, from your existing API credentials, to test and verify your SMS API credentials by sending a sample message to a designated device.

  6. Fill in the Number and Message fields and click Verify connection.

    note important
    IMPORTANT
    The message must be structured to align with the provider’s payload format.

After creating and configuring your API credential, you now need to create your Webhook and a channel configuration for your RCS messages. Learn more

Configure API credentials for MMS sinch-mms

IMPORTANT
Along with MMS setup, you also need to create Sinch API credentials specifically for tracking inbound messages and managing consent requests.

To configure Sinch MMS to send MMS with Journey Optimizer, follow these steps:

  1. In the left rail, browse to Administration > Channels > SMS Settings and select the API Credentials menu. Click the Create new API credentials button.

  2. Configure your MMS API credentials, as detailed below:

    • SMS vendor: Sinch MMS.

    • Name: enter a name for your API credential.

    • Project ID, App ID and API Token: follow the steps below to gather your MMS API credentials.

      • For Project ID and App ID: Access the Conversation API Overview page of your Sinch project on your Sinch Dashboard.
      • For API Token: Obtain the Access keys for your Sinch Project and generate a Base64 API Token out of your Sinch Project Access keys.

  3. Click Submit when you finished the configuration of your API credentials.

  4. In the API Credentials menu, click the bin icon to delete your API credentials.

  5. To modify existing credentials, locate the desired API credentials and click the Edit option to make the necessary changes.

After creating and configuring your API credential, you now need to create your Webhook and a channel configuration for your RCS messages. Learn more

Configure API credential for RCS

RCS (Rich Communication Services) messaging is supported in Journey Optimizer through Sinch, allowing the sending of basic messages using verified business profiles with branding elements such as logos and sender names.

Native RCS authoring requires Sinch RCS. Twilio, Infobip, and other providers must use a custom provider integration.

Note that messages automatically fall back to SMS when the profile’s device does not support RCS or is temporarily unreachable via RCS.

To configure Sinch RCS to send RCS with Journey Optimizer, follow these steps:

  1. In the left rail, browse to Administration > Channels > SMS Settings and select the API Credentials menu. Click the Create new API credentials button.

  2. Configure your RCS API credentials, as detailed below:

    • SMS vendor: Sinch RCS.

    • Name: enter a name for your API credential.

    • Project ID, App ID and API Token: enter the project ID, app ID, and API token from your Sinch RCS account.

    • Service Plan ID: enter the service plan ID associated with your Sinch account.

    • SMS API Token: enter the SMS API token from your Sinch account.

  3. Optionally, enable the Use custom dataset for inbound option to store inbound RCS messages in a custom dataset. Learn more

  4. Set the API rate limit (requests per second) to cap the maximum number of API calls per second, use your provider’s recommended value to avoid throttling, or leave it at 0 for unlimited requests.

  5. Click Submit when you finished the configuration of your API credentials.

  6. In the API Credentials menu, click the bin icon to delete your API credentials.

  7. To modify existing credentials, locate the desired API credentials and click the Edit option to make the necessary changes.

After creating and configuring your API credential, you now need to create your Webhook and a channel configuration for your RCS messages. Learn more

recommendation-more-help
journey-optimizer-help