Bulk Move Files
Moves a batch of an owner’s files into one folder (or to the owner’s top
level) in a single transactional request — the batch counterpart of the
folderId move on PATCH /files/{fileId}, for reorganizing an entity’s
whole document set without one request per file.
The entityType + entityId name the owner whose placements move. Only
that owner’s placement of each file moves: a file shared onto other
entities keeps its placements there untouched. The target folderId must
belong to the same owner; folderId: null moves the files to the owner’s
top level.
All-or-nothing. If any fileId is unknown, belongs to another company,
or is not placed under the requesting owner, the WHOLE request is rejected
and NOTHING moves — a 404. If the target folderId belongs to a
different owner (or does not exist), the whole request is rejected with a
400.
Batch size is capped at 100 ids. More than 100, or an empty fileIds
array, is a 400.
Required permission: company.file:update
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
Body
The owner entity type, as a lowercase kebab-case slug (e.g. exposure, quote, company). The internal-only invoice owner is not addressable here.
"quote"
The owner entity id. null only for the company-level owner (entityType: company); required for every other owner.
The files to move. 1–100 ids, each placed under the requesting owner; duplicates move once.
1 - 100 elementsThe destination folder, which must belong to the requesting owner. null moves the files to the owner's top level.
Response
The batch moved; the ids of the files whose placement moved
The ids of the files whose placement moved
