Skip to main content
Vault stores file artifacts and their versions. The v2 file APIs work across applications; filing APIs reference these artifacts by ID.
  • POST /api/v2/files/uploads: prepare signed PUT instructions.
  • POST /api/v2/files/uploads/complete: confirm stored bytes and return artifacts.
  • GET /api/v2/files/{fileId}/text: read a bounded chunk of existing extracted text.
  • GET /api/v2/files/{fileId}/download: get a signed redirect for an original file version.
Start with Upload files for the upload walkthrough. See Read and cite document evidence for text, downloads, and version handling. The Files API reference contains the request and response schemas. A Mission Control is required only when selecting an @mc upload destination. For filing documents, follow the filing guide to select the filing’s MC and set record ownership before uploading.