Infobip API Authentication

How to authenticate Infobip API requests: one Bearer API key plus a connectionId. MindCloud stores your Infobip API key securely — set it once, never resend it.

Every Infobip API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Infobip account. This page covers both, plus exactly how to send them, so you do not need to visit any other page to get authenticated.

Steps to authenticate

Create a MindCloud account at app.mindcloud.co if you do not already have one.
Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
Create a Infobip connection in Connections. Infobip uses an API key. You generate the key in your Infobip account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
Copy the connection’s connectionId — you will send it on every request alongside your MindCloud API Key.

How requests are authenticated

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected Infobip account that should run the action. MindCloud stores and refreshes the Infobip credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions.

For example, calling Get Outbound SMS Delivery Reports with an Infobip connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/infobip/actions/get-outbound-sms-delivery-reports/run" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "arguments": {}
}'

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which Infobip account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect Infobip with an API key

You need an Infobip account and an API key with the scopes required for the SMS, Email, Account, or 2FA endpoints you plan to use.

Open your Infobip account
Sign in to your existing Infobip account, or create a free trial account first if you do not have one yet.
Infobip account
Create or review your API key
Use Infobip's API authorization guide to create an API key or confirm that your existing key has the scopes required for the endpoints you want to use in this app.
API authorization
Confirm the required scopes
Make sure the key includes the scopes your workflows need. For example, SMS sending uses scopes such as message:send or sms:message:send, Email actions use email:manage or email:message:send, Account balance uses account-management:manage, and 2FA actions require 2fa scopes.
Paste the API key into MindCloud
In the MindCloud connection form for Infobip, paste only the raw API key value into the API Key field.

Keep your key safe

Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs. Anyone with the key can call the Universal API as your MindCloud account, across every connection you have created.