Sign inGet started
Docs
Get started

CalendarLink API Authentication

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

Every CalendarLink API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your CalendarLink 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

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a CalendarLink connection in Connections. CalendarLink uses an API key. You generate the key in your CalendarLink account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
  4. 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 CalendarLink account that should run the action. MindCloud stores and refreshes the CalendarLink 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 Current User with an CalendarLink connection looks like this:

curl --request POST \
  --url "https://connect.mindcloud.co/v2/universal/apps/calendarLink/actions/get-current-user/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 CalendarLink account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect CalendarLink

CalendarLink publishes demo API credentials in its official AI instructions. Use those for initial testing, then replace them with your tenant-specific credentials after signup.

  1. Open the CalendarLink AI instructions

    Use the official CalendarLink page that documents the Bearer-token API flow and the published demo credentials.

    AI instructions
  2. Copy the Bearer token into the MindCloud connection

    In the API Event Creation section, copy the token value that appears after `Bearer ` in the Authorization example. Paste that value into the MindCloud API key field for this connection.

  3. Copy the public organisation ID you will use in org-scoped actions

    For endpoints like contacts and events, copy the published organisation ID from the same instructions page. Keep it available for action inputs or future defaults.

  4. Copy a collection ID if you plan to create events

    If you want to use event-creation actions, also copy the default collection ID from the instructions page or replace it later with a tenant-specific collection ID after signup.

  5. Replace the demo credentials after signup

    When you have a real CalendarLink tenant, swap the shared demo token and IDs for your own tenant-specific values before using the app for production data.

    CalendarLink app

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.