Content Snare API Authentication

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

Every Content Snare API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Content Snare 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 Content Snare connection in Connections. Content Snare uses OAuth. When you create the connection, you are redirected to sign in to Content Snare 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 Content Snare account that should run the action. MindCloud stores and refreshes the Content Snare 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 Requests with an Content Snare connection looks like this:

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

Set up your Content Snare OAuth app

You need a Content Snare admin user. Content Snare only allows admin users to use the API and approve OAuth access.

Open the API settings page
In Content Snare, select your avatar, then Settings. Under Integrations, open API.
Create a new API application
Select Create a New Application, then enter an application name, description, and this redirect URL: https://api.mindcloud.co/v1/oauth/contentSnare/callback.
Choose the required scopes
Enable the scopes needed for the MindCloud wrapper: write_clients, write_team_members, write_requests, review_requests, read_templates, read_requests, read_team_members, read_clients, and administration.
Enter the OAuth credentials in MindCloud
Use the Client ID and Client Secret from Content Snare when you create the MindCloud test connection for this app.
Authenticate the connection
Start the OAuth connect flow in MindCloud and approve access as a Content Snare admin user.

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.