Files.fm Cloud Files and Storage API Documentation

Official documentation: https://api.files.fm/api/docs/. The same Markdown sources produce the interactive documentation, complete HTML pages, and public MCP documentation resources. JavaScript and authentication are not required to read documentation.

Start an integration

• DVS tasks: start with the tasks quickstart, then the DMS reference. DMS and DVS refer to the same data-management API. Discover project, user, and dropdown IDs before creating records.
• Storage: start with the storage quickstart. Prefer V2 where an equivalent exists; V1 remains supported for compatibility.
• AI clients: connect to https://api.files.fm/api/mcp to search and fetch this documentation without a token. Private file tools require their own authentication. MCP does not read structured DVS records or create/update tasks.

REST V2 uses POST form fields; DVS uses POST JSON with user and user_access_token. MCP uses its documented Bearer authentication. DAV/FTP credentials are protocol-specific; do not interchange these formats.

References

• Files.fm API documentation: the complete, merged API reference. Covers REST API V2 (data storage, CRUD, e-signature, AI API, upload form, embedding, previews, conversion, end-to-end encryption keys) and all V1 endpoints, plus authentication methods and ROOT folder/account info.

• MCP: public documentation, authenticated file access/search, and optional authorized folder creation, upload, rename and move tools.

• DMS API: Document Management System API — currently tasks (create/read/update/comment), projects (read), contact persons (create/read/update), and clients (read). Covers authentication, field schema discovery, filtering, pagination, and request/response examples.

• CalDAV and CardDAV: calendar and address-book APIs over HTTPS, including authentication, discovery, event/contact CRUD, synchronization, and shared-calendar permissions.

• WebDAV and FTP/FTPS: network-drive and file-transfer protocols, authentication, locking, and operational limits.

Machine-readable sources

• OpenAPI YAML and OpenAPI JSON: REST V2, legacy V1, and public DVS actions. DAV protocols use their own XML contracts; MCP tool schemas are discovered through MCP.
• Swagger UI: interactive REST explorer. Requests can change data; use a dedicated test account for write examples.
• Documentation index, full Markdown collection, and document catalog.

The index is a discovery aid, not a guarantee that every AI product fetches links or supports a particular content type. If a client cannot retrieve Markdown, use the linked HTML version. Never invent API endpoints or organization-specific IDs when retrieval fails.

For production integrations, prefer API V2 where available. V1 endpoints remain for compatibility with existing integrations and can be used, while no V2 endpoint exists.

For DMS API details that are not yet published here, contact Files.fm.