Campaign Monitor API Authentication

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

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

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

How to connect Campaign Monitor

An app owner must register a Campaign Monitor OAuth application and configure its Client ID and Client Secret on this MindCloud app before end-user connections can complete. When Campaign Monitor asks for a redirect URI, use the callback URL shown by MindCloud during connection setup.

Sign in to Campaign Monitor
Sign in to the Campaign Monitor account that owns the clients, lists, campaigns, and templates you want MindCloud to access.
Register an OAuth application
In Campaign Monitor, open Integrations from the top navigation, then choose OAuth Registration in the right sidebar. Register a new OAuth application and keep the generated Client ID and Client Secret.
Configure the MindCloud app
Have a MindCloud app owner add the Campaign Monitor Client ID and Client Secret to this app configuration before any end-user tries to connect.
Approve access
Once the app owner has configured the client credentials, start the Campaign Monitor connection in MindCloud, review the requested permissions, and approve 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.