Docs

HelpCrunch API Authentication

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

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

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/helpCrunch/latest/actions/list-customers" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

The Authorization: Bearer <your MindCloud API Key> header authenticates you to MindCloud; the connectionId tells MindCloud which HelpCrunch account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.

Connect HelpCrunch

You need a HelpCrunch account with REST API access and a permanent API key.

  1. Sign in to HelpCrunch

    Open your HelpCrunch workspace and sign in with an account that can access API settings.

    HelpCrunch
  2. Open the REST API area

    Follow HelpCrunch's REST API documentation to the authorization settings for your workspace and locate the permanent API key used for REST requests.

  3. Copy the permanent API key

    Copy the permanent API key exactly as shown. HelpCrunch documents REST API authentication with the Authorization header using Bearer plus your API key.

  4. Paste the key into MindCloud

    Return to MindCloud and paste the HelpCrunch API key into the test connection or connection form.

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.