Ninox API Authentication
How to authenticate Ninox API requests: one Bearer API key plus a connectionId. MindCloud stores your Ninox API key securely — set it once, never resend it.
Every Ninox API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Ninox 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 Ninox connection in Connections. Ninox uses an API key. You generate the key in your Ninox 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 Ninox account that should run the action. MindCloud stores and refreshes the Ninox 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 Download File with an Ninox connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/ninox/actions/download-file/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 Ninox account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect Ninox with a Personal Access Token
You must sign in as the workspace owner in Ninox Public Cloud. Only the workspace owner can generate the token.
- Open Ninox Public Cloud
Sign in to the Ninox Public Cloud web app with the workspace owner account you want to connect.
Ninox Public Cloud - Open Integrations from the Actions gear icon
In the Ninox web app, open the Actions gear icon and choose Integrations.
Actions gear icon → Integrations - Generate and copy the Personal Access Token
Select Generate, then copy the new token and keep it available while you finish the MindCloud connection.
- Paste the token into MindCloud
Return to the MindCloud connection form and paste the token into the API key field for this Ninox 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.