ExaVault API v2.0

The ExaVault API v2.0 supports existing integrations that use resource-based URLs under /api/v2/, with HTTP methods such as GET, POST, PATCH, and DELETE identifying the operation. The legacy API overview explains support for migrated integrations and when to use the modern Files.com API.

Connecting to the API

Use your account's subdomain address, such as mysite.files.com, for all legacy version 2.0 calls. ExaVault API Authentication explains the API keys and access tokens these calls use.

Request Values

Resource operations can identify a file or folder by its path or internal ID. When a request parameter accepts either, prefix an ID with id:, such as id:31415926535. Endpoints that take an ID in the URL instead use the numeric ID as the path parameter.

The Create a User and Update a User requests take permissions as an object of named boolean values. This differs from the CSV permission string used by v1.2. The user permission translation explains how those legacy permissions map to Files.com access.