Integration settings for EngageOne Deliver

To define the settings used when making REST calls to EngageOne Deliver, in Designer, click Config and then go to the Integration tab.

EngageOne Deliver's SMS REST URL For conversations initiated by EngageOne Deliver enter the EngageOne Deliver's SMS endpoint as implemented using the Deliver API. For example http://server/resource/v1/messages/sms. This is the URL that Converse will call to send a message.

There is a different endpoint for conversations that are initiated by a third-party with a specific user. For example, a dental practice uses the bot to send reminders to clients of upcoming appointments, with the option to change their appointment. The format of the REST URL is:

POST: http://{server}/api/v1/pbSms/init/{tenantID}/{botID}

For more details, see Allowing a third-party to trigger the bot.

Authorization If EngageOne Deliver is configured to use basic authentication then enter the word Basic followed by the Base64-encoded user:password string. The user and password is set below. For example if you set User to demo and Password to test then enter:

Basic ZGVtbzp0ZXN0

You can encode the user:password string using any encoding tool, including any online tool (for example search for base64 encode).

From Address Optional. Enter the phone number that will be seen by the user when receiving SMS texts.
URL to use in EngageOne Deliver Copy the URL shown here to use in EngageOne Deliver when configuring the template association's Notification End Point field. It takes the format:


User, Password This user provides the security context for calls from EngageOne Deliver to Converse. This is used to do the basic authorization validation.
Sample Body for EngageOne Deliver's template This is a sample of the body to use in EngageOne Deliver when setting up the template.
Note: Change the sample authentication header to the user and password you entered.

For an overview of how to configure EngageOne Deliver, see EngageOne Deliver integration steps.