SDKs & 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.
Use the Files.com API and SDKs for new development. The ExaVault Legacy APIs support applications that were already in production when their accounts migrated to Files.com. That compatibility reference is for maintaining those existing integrations; new applications must use the modern Files.com API and SDKs.
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. Set the login name to @api- followed by either the key's ID or the key's name, for example @api-5373469 or @api-botsync, and use the API key itself as the password. The value after @api- identifies the key, not the user who owns it.
Planning an Integration
Start with the work your application needs to perform and the access it requires. Use a dedicated API key so the integration's credentials can be managed independently. A supported SDK handles common API tasks in your programming language, leaving your code to express the business workflow.
If a custom application is not necessary, a script or existing connector may meet the same need with less code to maintain. Best Practices for Integrating with Files.com helps you make that choice. For implementation details, use the API and SDK reference.