SDK & APIs
The Files.com REST API and SDKs are for building custom integrations. With them, you can connect Files.com to your own applications. Common uses include automating workflows, managing users and permissions programmatically, or pulling platform data into your own systems.
Files.com practices API-first development and builds its own products on the same SDKs we publish to customers. When a new feature is released, its API documentation and SDKs are updated automatically to support it.
What You Can Build With Files.com APIs
Customers use the APIs to power a wide range of custom integrations with Files.com. A few common patterns:
- Sync the user list with an external system or database that doesn't support Single Sign-on (SSO), using a custom solution to bulk import and sync users from the other system.
- Automatically generate personalized Share Links for digital order fulfillment.
- Pull platform metrics, such as History Exports or Usage Snapshots, into BI platforms and reporting tools.
You can also use an API key as the password to sign in to FTP, SFTP, and WebDAV. This is useful when you have scripts or applications that need to sign in using those protocols. In this case, the user login name will be @api-[key-id or API key name] and the password will be the API key content.
Where to Start
Best Practices for Integrating with Files.com covers how to choose between SDKs, the CLI application, iPaaS connectors, and file transfer protocols.
The API Keys pages cover creating and managing API keys for authentication, and restricting which users can create them.
Official Files.com SDKs covers the supported programming languages, common failure patterns, and how Files.com handles SDK versions.
If you're building an AI application to interact with your Files.com site, the MCP Server is built for LLM-based clients and AI agents.
Full API and SDK reference lives at https://developers.files.com/.