Sign inGet started
Docs
Get started

SafetyCulture API Authentication

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

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

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

Create a SafetyCulture API token

You need a SafetyCulture account with API access. For shared production integrations, SafetyCulture recommends using a service user token instead of a personal user token.

  1. Create a service user token (recommended)

    Follow SafetyCulture's official service-user guide to create a service user, assign the right permissions, and generate its API token.

  2. Use a personal API token only if you do not manage service users

    If this connection should mirror your own account access, follow SafetyCulture's official user-token guide and generate a personal API token from the web app.

  3. Paste the token into MindCloud

    When MindCloud asks for the API Key value, paste the token you copied from SafetyCulture and save 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.