Files.com API Documentation
This is the complete API documentation for connecting to the Files.com API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet Files.com: Store files, manage folders, automate transfers, and orchestrate secure file operations. Keep reading to get started.
Quickstart
Before you run your first Files.com request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one Files.com connection — create or choose one in Connections. Note its
connectionId.
Every Files.com action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/filescom/latest/actions/{actionSlug}You need a MindCloud API Key and a Files.com connection. Then call an action such as Get Automation:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/filescom/latest/actions/get-automation" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
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. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
Files.com actions
All 38 published actions for this Files.com version. Each page documents the endpoint, arguments, and response controls.
- POSTBegin File Upload
- POSTCopy File or Folder
- POSTCreate Folder
- DELETEDelete File or Folder
- GETGet Automation
- GETGet Bundle
- GETGet File Download Link
- GETGet File or Folder Metadata
- GETGet Group
- GETGet Notification
- GETGet Project
- GETGet Site
- GETGet Site Usage
- GETGet Sync
- GETGet User
- GETGet Workspace
- GETList Automations
- GETList Bundles
- GETList File Comments
- GETList File History
- GETList Folder Contents
- GETList Folder History
- GETList Groups
- GETList History
- GETList Login History
- GETList Notifications
- GETList Permissions
- GETList Projects
- GETList Requests
- GETList Requests by Folder Path
- GETList Syncs
- GETList User History
- GETList Users
- GETList Workspaces
- PUTMove File or Folder
- PUTRun Automation Now
- PUTRun Sync Now
- PUTUpdate File or Folder Metadata
Related apps
More Content & Files apps on the Universal API, behind the same REST shape. Or browse all apps.