Ortto API Authentication
How to authenticate Ortto API requests: one Bearer API key plus a connectionId. MindCloud stores your Ortto API key securely — set it once, never resend it.
Every Ortto API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Ortto 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 Ortto connection in Connections. Ortto uses an API key. You generate the key in your Ortto account, then paste it in when you create the connection — MindCloud stores it securely and never returns it in a response.
- 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 Ortto account that should run the action. MindCloud stores and refreshes the Ortto 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 Export Campaign Data with an Ortto connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/ortto/actions/export-campaign-data/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 Ortto account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect Ortto with a custom API key
You need access to the target Ortto workspace and its region (US, EU, or AU).
- Sign in to Ortto
Open the Ortto workspace that you want MindCloud to connect to.
Login - Create a custom API data source
In Ortto, go to the Data sources area, start a new data source, then choose Custom API (advanced) and Get started.
- Finish the setup page
Enter a clear API name such as MindCloud, review the default merge strategy, and click Create.
- Copy the Private API key
On the Configuration page, copy the Private API key and keep it secure. You will paste this value into the MindCloud connection as the API key.
- Choose the API Base URL for this workspace region
Use https://api.ap3api.com for US workspaces, https://api.eu.ap3api.com for Europe, or https://api.au.ap3api.com for Australia. Enter the value without a trailing slash.
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.