CloudConvert API Authentication
How to authenticate CloudConvert API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes CloudConvert tokens for you.
Every CloudConvert API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your CloudConvert 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 CloudConvert connection in Connections. CloudConvert uses OAuth. When you create the connection, you are redirected to sign in to CloudConvert and approve access — MindCloud stores the resulting tokens and refreshes them automatically, so your integration never has to.
- 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 CloudConvert account that should run the action. MindCloud stores and refreshes the CloudConvert 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 Get Current User with an CloudConvert connection looks like this:
curl --request POST \
--url "https://connect.mindcloud.co/v2/universal/apps/cloudConvert/actions/get-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 CloudConvert account to run the action against. Missing or invalid Authorization returns 401, and a missing or mismatched connectionId returns 400.
Connect CloudConvert
You need a CloudConvert account and permission to create OAuth applications for that account.
- Open the CloudConvert OAuth applications area
Sign in to CloudConvert and navigate to the OAuth application management area for your account.
- Create an OAuth application for MindCloud
Create a new OAuth application for MindCloud and keep the application detail page open after it is created.
- Save the MindCloud redirect URI in CloudConvert
Copy the redirect URI shown in the MindCloud connection dialog and add that exact value to the CloudConvert OAuth application before saving your changes.
- Paste the client credentials into MindCloud
Return to MindCloud and paste the CloudConvert client ID and client secret into the connection form, then continue with CloudConvert authorization.
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.