Sign inGet started
Docs
Get started

CreateSend API Authentication

How to authenticate CreateSend API requests: one Bearer API key plus a connectionId. MindCloud stores your CreateSend credentials — no auth headers to build.

Every CreateSend API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your CreateSend 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 CreateSend connection in Connections. CreateSend uses a username and password. You enter them when you create the connection — MindCloud stores them securely so your requests never carry raw credentials.
  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 CreateSend account that should run the action. MindCloud stores and refreshes the CreateSend 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 CreateSend connection looks like this:

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

CreateSend API Key Setup

You need a Campaign Monitor API key from Account Settings. For this auth method, the API key is used as the Basic username.

  1. Open the CreateSend test connection

    Use the draft app's default Basic auth connection form.

  2. Paste the API key into Username

    Use the long Campaign Monitor API key value as the Basic username.

  3. Set Password to x

    Campaign Monitor ignores the password for API-key auth. If blank passwords are not allowed, use x.

  4. Run Get Clients

    The credential test action calls GET /clients.json. This endpoint does not require a clientId parameter.

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.