ExaVault Legacy APIs

---

Files.com acquired ExaVault, another Managed File Transfer service, in 2021. As of 2023, the ExaVault service has been integrated into the "mainline" Files.com service.

ExaVault has two legacy API versions, and both are still supported and will be supported in perpetuity on Files.com.

Support is limited to applications that were already in production using these APIs as of 2022 or earlier. New applications should use the modern Files.com SDKs and API.

These documentation pages are maintained for reference purposes only, and to allow current applications to be supported.

Files.com has preserved the interfaces and operations of the ExaVault legacy APIs as best as possible. The vast majority of customers should find that their API integrations continue functioning without any intervention required.

Developers should not need to change anything about existing applications to use the ExaVault API on Files.com. Existing code should continue to work after migration the same way it did pre-migration.

It is not possible to run legacy API code within a web browser session once a site has been migrated to the Files.com platform.

If you have implemented a client-side web application that is making requests to the legacy ExaVault API, this is not supported after migration to the Files.com platform. You should instead create a wrapper API on the server for your clients to interact with; your wrapper code is responsible for communicating with the legacy API, or with the Files.com API. This prevents exposing your authentication tokens to your clients.

After your account is migrated, the URLs used by API code will continue to function. If you accessed the API through the accountname.exavault.com address, that same address will still work. If you used api.exavault.com as the host name, that host will continue to work except when certain conditions apply.

If you create new API keys after your site has been migrated, you cannot use the api.exavault.com hostname for the legacy API.

If you use the v1.2 authenticateUser function to log in with a user's credentials, you must use your account's subdomain address (such as accountname.exavault.com or accountname.files.com).

The hostname of api.exavault.com was not officially supported on the legacy platform for version 2.0, but happened to work due to that network's configuration.

After your account has migrated to the modern platform, you must use your account's subdomain address, such as accountname.exavault.com or accountname.files.com with legacy API version 2.0.

All of your existing API keys will be migrated along with the rest of your account data and can be used the same way they were before.

Access tokens associated with a specific user, which were created through the ExaVault web file manager will be migrated along with the rest of your account data.

Temporary access tokens will not be migrated, so you will need to retrieve a fresh token using the authenticateUser method.

For all of the supported methods, the previously published SDKs should continue to work without modification. The contents of some responses may now contain placeholders or empty values, but SDKs should continue to function as expected without needing an update.

If you have configured a custom URL for your new Files.com site, you cannot use that address to interact with the legacy ExaVault APIs. You must use your subdomain address, either as accountname.exavault.com or accountname.files.com.