Using Files.com API Keys with ExaVault APIs

You can create new API keys on your Files.com site and supply those to the legacy ExaVault API.

If you create new API keys, your API code cannot use https://api.exavault.com as the base URL.

The legacy ExaVault API supported two different methods of authentication - you could use the v1.2 GET|POST /authenticateUser to create a new access token for each session, providing the user's credentials; you could also use permanently-assigned access tokens (created via the legacy ExaVault web file manager).

Tokens created in either method are compatible with both versions of the legacy ExaVault API.

To create new API Keys for your existing code after your site has migrated, you'll either create a site-wide API Key (if your code makes use of the v1.2 GET|POST /authenticateUser function) or a user-specific API Key (if your code relied on a permanent access token).

1. Create a new site-wide key in your Files.com account.

2. Supply that key in the api_key ( or api-key )header when making a request to /authenticateUser

3. In subsequent requests to the legacy v1.2 API, provide the returned access token for the access_token parameter and the site-wide key for the api_key ( or api-key )header. If you're using any legacy v2.0 endpoints, supply that key in both the ev-api-key and ev-access-token headers on all requests

1. Create a new API Key for a specific user in your Files.com account.

2. Supply that key in both the ev-api-key and ev-access-token headers on all requests to the Legacy v2 API. For any requests to the Legacy v1.2 API, supply the user key in the api_key ( or api-key ) header and access_token parameter.