Rossum API Authentication

How to authenticate Rossum API requests: one Bearer API key plus a connectionId. MindCloud stores your Rossum API key securely — set it once, never resend it.

Every Rossum API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Rossum 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 Rossum connection in Connections. Rossum uses an API key. You generate the key in your Rossum 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 Rossum account that should run the action. MindCloud stores and refreshes the Rossum 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 Retrieve Current User with an Rossum connection looks like this:

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

Connect Rossum with a bearer token

You need the Rossum workspace URL for your account and a valid bearer token.

Open your Rossum workspace
Sign in to the Rossum tenant you want to connect so you can confirm the correct workspace host for your account.
Rossum workspace
Create or retrieve a bearer token
Use Rossum's API authentication flow to obtain a bearer token for the same account. The API documentation is the canonical source for current auth behavior.
Rossum API Documentation
Paste the token into MindCloud
In the Rossum connection form, paste the token into the API Key field. MindCloud sends it as an Authorization bearer token for Rossum API requests.

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.