Vaults and Access
Use Vault discovery and user/team endpoints before acting on documents.
Most document actions start by choosing a Vault. Vaults represent document workspaces for a team, business unit, matter, or process.
Start with Vault discovery
Call listVaults before upload, search, report, export, or workflow operations. This gives the caller the Vault IDs it is allowed to use and prevents agents from inventing identifiers.
Users and assignments
Use team and Vault user endpoints when assigning work, filtering by assignee, or preparing approval and review workflows. User IDs and team access should be discovered from the API rather than hard-coded.
Access model
The API evaluates the caller's bearer key. MCP clients should forward the user's own TextMine API key so requests resolve to the right organisation, permissions, Vaults, and integrations.