BotStar API Authentication
How to authenticate BotStar API requests: one Bearer API key plus a connectionId. MindCloud stores your BotStar API key securely — set it once, never resend it.
Every BotStar API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your BotStar 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 BotStar connection in Connections. BotStar uses an API key. You generate the key in your BotStar 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 BotStar account that should run the action. MindCloud stores and refreshes the BotStar 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 Bots with an BotStar connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/botStar/actions/list-bots/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 BotStar account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Set up your BotStar API Token
Sign in to the BotStar workspace that owns the bots and CMS data you want to manage.
- Open your BotStar profile
Go to your BotStar profile page where the API Token is shown.
Profile - Copy the API Token
Copy the value from the API Token field and paste it into your MindCloud BotStar connection.
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.