SurveyCTO API Authentication

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

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

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

Set up a SurveyCTO basic-auth connection

You need access to the SurveyCTO server at https://mindcloudsurvey.surveycto.com and permission to manage users or roles.

Sign in to your SurveyCTO server
Open your SurveyCTO server and sign in with an account that can manage server settings, users, or roles.
Confirm API access is enabled for the connection user
In the Configure area, review the user role and make sure it grants API access for the SurveyCTO resources you plan to use.
Create or choose the connection user
In the same Configure area, create a dedicated user or choose an existing one for MindCloud, then keep the username and password ready.
Enter the connection details in MindCloud
Use the server base URL https://mindcloudsurvey.surveycto.com together with that username and password when you create the SurveyCTO test 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.