Quaderno API Authentication

How to authenticate Quaderno API requests: one Bearer API key plus a connectionId. MindCloud runs the OAuth flow and refreshes Quaderno tokens for you.

Every Quaderno API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Quaderno 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 Quaderno connection in Connections. Quaderno uses OAuth. When you create the connection, you are redirected to sign in to Quaderno 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 Quaderno account that should run the action. MindCloud stores and refreshes the Quaderno 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 Tax Codes with an Quaderno connection looks like this:

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

Prepare your Quaderno connection

You need access to a Quaderno sandbox or live account where you can create apps for Quaderno Connect Standard accounts.

Open Quaderno's Standard Accounts guide
Use Quaderno's official onboarding guide so you create the app in the correct account type and environment.
Quaderno Developers → Guides → Connect → Onboard Standard accounts
Create a Quaderno app
While signed in to Quaderno, create a new app and enter your app name, website URL, support email, and the MindCloud callback URL shown in this connection form.
Keep the environment consistent
If you are testing in Quaderno Sandbox, create the app in Sandbox and complete the OAuth flow there. Sandbox and production accounts use separate credentials.
Finish the MindCloud connection
Enter the Client ID and Client Secret from Quaderno here, save the connection, and then click Connect to complete the OAuth approval flow.

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.