Connect and authenticate Infobip with Fusion Service
Add a new confidential application in IDCS
When Infobip receives messages from your customers, it forwards those messages to the provided API. To do this, it must authenticate itself with IDCS. To enable authentication with IDCS, you need to set up a new confidential application.
See Add a Confidential Application to add the confidential application in IDCS.
- Set the following parameters and leave the others as their default value.
Application details parameters
Parameter Value Name Engage Messaging Description Application for authenticating API requests from Infobip. -
Skip configuring authorization, and configure the application as a resource server.
Set the following parameters and leave the others as their default value:
Resource server configuration parameters
Parameter Value Access Token Expiration 3600 seconds Primary Audience api Add (allowed scopes) Add / as a scope. - Finish configuring the application and make a note of the client ID and client secret for the new application as you'll need to provide these to Infobip later.
- Activate the new application.
Review this video for help configuring confidential applications in IDCS.
Configure authentication with Fusion Service for your SMS and WhatsApp channels
Now you set up your confidential application. For this, you'll need to configure authentication for your SMS and WhatsApp numbers.
To do this, contact Infobip for help in setting up oAuth2-based authentication for each of the numbers you intend to use with Fusion Service. Provide the following infromation:
| Field | Description |
|---|---|
| Access Token URL |
The URL will be as follows:
Replace |
| Scope | Set to api/ |
| Grant Type | Set to client_credentials. |
| Client ID and Secret |
Provide the credentials you noted earlier when creating the
confidential application.
Note: Client
credentials are sensitive. Ensure you secure channel to
send these to Infobip. |
| Engage Messaging REST API URL |
This is the URL Infobip will use to send messages to the Engage REST API. The URL will be of the following form:
Replace |