Docs

Fireberry API Authentication

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

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

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

Get your Fireberry API access token

Fireberry API access uses a personal API access token. The token identifies the system user whose data and permissions the API will use.

  1. Open your Fireberry profile

    Sign in to Fireberry, click your profile picture in the top-right corner, and choose Profile.

    Profile picture → Profile

  2. Open Account Security and then API Access Token

    In your profile, open the Account Security tab and then the API Access Token tab.

    Profile → Account Security → API Access Token

  3. Copy the token

    Copy the TokenID exactly as Fireberry shows it and store it securely.

  4. Paste the token into MindCloud

    Return to the MindCloud Fireberry connection form and paste the copied TokenID into the API key field.

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.