EARLY API Authentication

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

Every EARLY API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your EARLY 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 EARLY connection in Connections. EARLY uses an API key. You generate the key in your EARLY 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 EARLY account that should run the action. MindCloud stores and refreshes the EARLY 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 Generate Report with an EARLY connection looks like this:

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

Set up an EARLY bearer token

You need an EARLY API key and API secret so you can generate a bearer token outside MindCloud.

Generate or locate your EARLY API key and API secret
In EARLY, create or regenerate your API access pair and copy both values immediately.
Exchange the pair for a bearer token
Run a POST request to https://api.early.app/api/v4/developer/sign-in with a JSON body containing apiKey and apiSecret.
Copy the returned token
The response includes a token field. Copy that token value exactly, without adding the word Bearer.
Paste the token into the MindCloud connection
Use the returned token as the API key value in the EARLY connection. MindCloud will send it as Authorization: Bearer <token>.

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.