Tabidoo API Authentication
How to authenticate Tabidoo API requests: one Bearer API key plus a connectionId. MindCloud stores your Tabidoo API key securely — set it once, never resend it.
Every Tabidoo API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Tabidoo 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 Tabidoo connection in Connections. Tabidoo uses an API key. You generate the key in your Tabidoo 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 Tabidoo account that should run the action. MindCloud stores and refreshes the Tabidoo 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 Apps with an Tabidoo connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/tabidoo/actions/list-apps/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 Tabidoo account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect Tabidoo with an API token
You need a Tabidoo user account that can open User Settings and generate API tokens. Permissions follow the token owner or assigned role.
- Open User Settings
Sign in to Tabidoo and open User Settings from your profile menu.
- Open the API section
In User Settings, navigate to the API section.
- Generate a Bearer API token
Create a new API token and copy the full token value. Use that value as the API key in your MindCloud connection.
- Optional: copy the short API token for upload actions
If you plan to use file or image upload actions later, copy the short API token too. It is only needed for upload-specific actions and is not required for the initial verified action batch.
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.