Files.com API Authentication

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

Every Files.com API request through MindCloud needs two things: a MindCloud API Key and a connectionId for your Files.com 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 Files.com connection in Connections. Files.com uses its own authentication scheme. You provide whatever it requires when you create the connection — MindCloud handles the provider-specific details for you.
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 Files.com account that should run the action. MindCloud stores and refreshes the Files.com 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 Site with an Files.com connection looks like this:

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

Connect Files.com Header API Key

You need a Files.com account with permission to create API keys. Files.com does not use OAuth scopes here; the API key inherits the owning user's permissions, so use a site-admin service user when you want admin actions such as Users, Groups, Permissions, Workspaces, Site Settings, Syncs, Automations, or audit history.

Create or copy a Files.com API key
In Files.com, open API Keys and create a key with the permissions you want MindCloud to use. Copy the API key value.
Documentation → SDK and APIs → API Keys
Enter your Files.com site URL
Enter your full Files.com site URL, for example https://mindcloud3.files.com. Do not add /api/rest/v1.
Paste the API key
Paste the API key into the API Key field. MindCloud sends it only in the X-FilesAPI-Key header for this auth type.

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.