Skip to main content
Knowledge documents are supplementary files like W-9s, COIs, and general attachments that are separate from contracts. They live in a dedicated knowledge_document table and have no impact on the existing contract (Document) model.

​
Key characteristics

PropertyDescription
Separate storageOwn table, independent from contracts
Supported formatsPDF, DOCX, XLSX, PNG, JPG
Soft deleteArchived, not permanently deleted
Org-scopedEvery document belongs to an organization

​
Upload flow

  1. Presign — Call POST /api/knowledge/presign with filename, organization, and content type. Receive a presigned S3 POST (url + form fields) and a knowledge_document_uid.
  2. Upload — Build a FormData from the returned fields, append the file, and POST directly to the S3 URL.
  3. Confirm — Call POST /api/knowledge/confirm with the knowledge_document_uid and organization. The server verifies the file exists in S3, checks the file size (max 25 MB), and starts a background workflow to create the database record.

​
Endpoints

List documents

Paginated, searchable document list

Create document

Finalize an uploaded file as a knowledge document

Update document

Rename a knowledge document

Delete document

Soft-delete (archive) a knowledge document