Twilio API Authentication

How to authenticate Twilio API requests: one Bearer API key plus a connectionId. MindCloud stores your Twilio credentials — no auth headers to build.

Every Twilio API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Twilio 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 Twilio connection in Connections. Twilio uses a username and password. You enter them when you create the connection — MindCloud stores them securely so your requests never carry raw credentials.
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 Twilio account that should run the action. MindCloud stores and refreshes the Twilio 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 List Messages with an Twilio connection looks like this:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/twilio/latest/actions/list-messages" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

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

Set up your Twilio API Key connection

Sign in to the correct Twilio account or subaccount in the Twilio Console. Twilio recommends API keys for production use instead of the Account SID and Auth Token pair.

Create a Twilio API key in the Console
In Twilio, click Admin > Account management. Under Keys & credentials, open API keys & tokens, then click Create API key. Choose Standard for most MindCloud use cases. Choose Restricted only if your team needs fine-grained permissions. Use Main only if you specifically need access to Twilio Accounts or Keys endpoints.
Copy the API Key SID and Secret
On the Copy secret key page, copy the API Key SID and the Secret, then store the Secret somewhere secure before leaving the page.
Copy the Twilio Account SID
Open the Twilio Account Dashboard and copy the Account SID for the account that owns the resources MindCloud should use.
Enter the credentials in MindCloud
Paste the API Key SID into Username, the API Key Secret into Password, and the Twilio Account SID into the Account SID field.
Fill in optional messaging fields only if your workflows need them
If your workflows send from a specific Twilio number, fill in Twilio Phone Number. If they send through a Messaging Service, fill in Twilio Messaging Service SID instead.

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.