Datarooms

List datarooms

Paginated list of datarooms for the authenticated team.

Create a dataroom

Create a new dataroom. Documents are added separately.

Get a dataroom

Returns dataroom metadata including document and folder counts. Accepts either the internal id or the `dr_…` public id.

Update a dataroom

Partial update of dataroom metadata. Documents are managed via the dataroom-documents endpoints, not here.

Delete a dataroom

Permanently deletes a dataroom and its document/folder mapping. The underlying documents are not deleted — only the dataroom and its membership rows.

Attach an existing document to a dataroom

Add an already-uploaded document to a dataroom, optionally placing it inside a dataroom folder. The document must belong to the same team as the dataroom; cross-team attaches are refused. Frozen datarooms refuse new attachments.

List documents in a dataroom

Returns DataroomDocument rows (the join between a dataroom and an underlying Document), ordered by folder then orderIndex.

List folders in a dataroom

Returns folders inside a dataroom. Use `parent_id=root` to list top-level folders, or `parent_id=<id>` for direct children of a specific folder. Without `parent_id` returns every folder in the dataroom.

Create a dataroom folder

Create a folder inside a dataroom. Path is derived server-side from name + parent. On sibling-name collision a numeric suffix is appended. Default permissions (matching the dashboard's create flow) are applied.

Get a dataroom folder

Returns a single folder inside a dataroom.

Update a dataroom folder

Rename a folder or update its icon/color. Renaming rewrites the `path` of this folder and every descendant in a single transaction.

Delete a dataroom folder

Delete a folder inside a dataroom. Refuses non-empty folders unless `cascade=true`. Cascade deletes nested folders and detaches every dataroom-document inside them — the underlying documents in the team library are kept.

Move a dataroom folder

Reparent a folder within a dataroom. Refuses moves into the folder itself or one of its descendants, and refuses if the target parent already has a sibling with the same slug. Descendant `path`s are rewritten in a single transaction.