TimeRex API Authentication

How to authenticate TimeRex API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes TimeRex tokens for you.

Every TimeRex API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your TimeRex 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 TimeRex connection in Connections. TimeRex uses OAuth. When you create the connection, you are redirected to sign in to TimeRex and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
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 TimeRex account that should run the action. MindCloud stores and refreshes the TimeRex 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 with an TimeRex connection looks like this:

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

Connect TimeRex OAuth

You need Team Settings access in TimeRex, a public HTTPS redirect URI, and the scopes your app will request.

Open Developer Tools in TimeRex
Sign in to TimeRex, open Team Settings, and select Developer Tools.
Dashboard → Team Settings → Developer Tools
Register your OAuth client
Create an OAuth client and fill in the application name, description, logo, domain, terms link, privacy policy link, HTTPS redirect URI, and the scopes you want to request. Then copy the client ID and client secret.
Allow API access to team information
Open Team Settings > Security and enable the setting that allows the API to get team information.
Dashboard → Team Settings → Security
Finish the MindCloud connection
Return to MindCloud, enter the client ID and client secret, then complete the OAuth popup to authorize the 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.