ExaVault Legacy APIs
Files.com acquired ExaVault, another Managed File Transfer service, in 2021. Since then, the ExaVault service has been integrated into the mainline Files.com service.
ExaVault has two legacy API versions. Both are supported on Files.com and will continue to be supported in perpetuity. Support is limited to applications that were already in production using these APIs at the time of migration. New applications must use the modern Files.com SDKs and API.
These documentation pages are maintained for reference and to support existing applications.
ExaVault API Migration Notes
Files.com preserves the interfaces and operations of the ExaVault legacy APIs as closely as possible. Most customers find that their API integrations continue to function without any intervention.
Existing applications do not need code changes to use the ExaVault API on Files.com. Existing code continues to work after migration the same way it did pre-migration.
ExaVault API Keys Are Migrated
All existing API keys are migrated with the rest of the ExaVault account data and can be used the same way they were before.
Permanent Access Tokens Are Migrated
Access tokens associated with a specific user, created through the ExaVault web file manager, are migrated along with the rest of the account data.
Temporary access tokens are not migrated. A fresh token can be retrieved at any time using the v1.2 authenticateUser method.
Existing Code and SDKs Will Work
For all of the supported methods, the previously published SDKs continue to work without modification. The contents of some responses may now contain placeholders or empty values, but SDKs continue to function as expected without needing an update.
Legacy API Code Cannot Be Used Within a Web Browser Session
Legacy API code cannot run within a web browser session once a site has been migrated to the Files.com platform.
Client-side web applications that make requests to the legacy ExaVault API are not supported after migration to the Files.com platform. Instead, create a wrapper API on the server for clients to interact with. The wrapper code is responsible for communicating with the legacy API, or with the Files.com API. This prevents exposing authentication tokens to clients.
Connecting to the Legacy API
After an account is migrated, the URLs used by API code using API Keys that existed before the migration continue to function using the same addresses.
Connecting With New API Keys
Legacy code that uses api.exavault.com continues to work. For new API keys or access tokens created after a site has been migrated, the legacy API hostname must be the site's subdomain, such as mysite.files.com.
Custom URLs for Files.com Sites Cannot Be Used With ExaVault APIs
A custom URL configured for a new Files.com site cannot be used to interact with the legacy ExaVault APIs. The subdomain address, such as mysite.files.com, must be used for the legacy ExaVault APIs.
Use the Files.com API and SDKs for New Development
The ExaVault platform, and by extension the legacy ExaVault APIs, provided a limited set of features. Using the legacy ExaVault APIs prevents access to most of the features and functionality of the Files.com platform. We strongly urge developers to use the Files.com API and its optimized SDKs for new development to take full advantage of the Files.com platform.
The Files.com API offers access to all of the features in your site, including fine-grained user permissions, automations, IP address control, and history logs. We are continuously adding new functionality to our APIs and improving our SDKs.
Files.com offers SDKs in popular programming languages and provides developer-friendly features such as automatic pagination, automatic retries for file transfers, and parallelization of uploads and downloads.