Sign inGet started
Docs
Get started

QuickFile API Authentication

How to authenticate QuickFile API requests: one Bearer API key plus a connectionId. MindCloud handles QuickFile's custom auth scheme for you.

Every QuickFile API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your QuickFile 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

  1. Create a MindCloud account at app.mindcloud.co if you do not already have one.
  2. Generate a MindCloud API Key in API Keys. This is the Bearer token you send on every request. Keep it on your server.
  3. Create a QuickFile connection in Connections. QuickFile uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
  4. 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 QuickFile account that should run the action. MindCloud stores and refreshes the QuickFile 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 Account Details with an QuickFile connection looks like this:

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

Connect your QuickFile account

You need your QuickFile account number, your QuickFile API key, and the Application ID for the QuickFile app registration you want this connection to use.

  1. Open QuickFile account settings

    Sign in to QuickFile and open the account settings area for the QuickFile account you want to connect.

  2. Find your API key

    In account settings, locate the API key generated for that QuickFile account. This is the static key used to sign every API request.

  3. Open the QuickFile app registration you want to use

    Under 3rd Party Integrations, open the QuickFile app registration that should back this connection and copy its Application ID.

  4. Copy the account number

    Locate the QuickFile account number for the same QuickFile account that owns the API key.

  5. Create the MindCloud test connection

    In MindCloud, enter the account number, API key, and Application ID. Submission numbers and MD5 signatures are generated at request time and are not entered manually.

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.