Skip to main content
Documents have a dedicated section in the API Reference. The current Public API operates on documents belonging to a specific client in the authenticated company. All writes require an Idempotency-Key header. Registering a document stores an existing HTTP(S) URL; it does not upload a file. Archiving hides the document from Public API and company MCP document listings; it does not delete the document or its file from FITsociety or the external host. Company-wide document listing and management are not currently exposed through the Public API. Client routes do not provide a company-wide document collection.

List document folders

Required scope: documents:read Response fields:

List documents

Required scope: documents:read Validation: Response fields: Not exposed in v1: upload, delete, folder mutation, signed document download URLs, raw media, provider metadata, message IDs, or file contents.
Required scope: documents:write This endpoint stores metadata for a document managed outside FITsociety. It does not upload binary files and does not expose raw download links in list/read responses. Request body: Validation: Response fields:
Response (201 Created):

Update document metadata

Required scope: documents:write Allowed fields: name, documentUrl, externalUrl, mimeType, type, fileSize, and folderId. At least one field is required. The same name, URL, type, file-size, client, and folder validations as Link external document metadata apply. Response fields:

Archive document metadata

Required scope: documents:write Archive is a metadata-only soft archive. The document is excluded from Public API list responses after archiving. It does not delete a binary file from external storage. Response fields: