TeamUp API Authentication
How to authenticate TeamUp API requests: one Bearer API key plus a connectionId. MindCloud stores your TeamUp API key securely — set it once, never resend it.
Every TeamUp API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your TeamUp 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 TeamUp connection in Connections. TeamUp uses an API key. You generate the key in your TeamUp 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 TeamUp account that should run the action. MindCloud stores and refreshes the TeamUp 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 Calendar Configuration with an TeamUp connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/teamUp/actions/get-calendar-configuration/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 TeamUp account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect TeamUp
You need a TeamUp API key and a TeamUp calendar key. This wrapper does not accept the public TeamUp calendar URL code as a substitute for the calendar key.
- Request a TeamUp API key
Open TeamUp's API key request page and register your application.
API key request page - Open the calendar sharing settings
In TeamUp, open the web-based calendar settings application and go to the Sharing tab where calendar keys are managed.
- Copy a TeamUp calendar key
Create or copy the TeamUp calendar key that this connection should use. Use an admin-capable calendar key if you want sub-calendar create, update, and delete actions to work.
- Paste the credentials into MindCloud
Enter your TeamUp API key and your TeamUp calendar key in this 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.