Update File Placement (Move / Categorize per Entity)
Updates ONE placement’s organization — the folder it sits in (folderId)
and/or its free-text category label. Folder location and category are
per placement, so this is the way to re-folder or re-categorize a file
that is shared across several entities: address the placement to change
by its id (from
List File Placements
or the share response) — the file’s other placements are untouched. The
owner-less
Rename, Move, or Categorize File
endpoint returns 409 Conflict for these fields once a file is shared;
it also works on single-placement files, where either endpoint can be
used.
Send only the fields you want to change — at least one must be present.
Set folderId to a folder id to move the placement into that folder
(the folder must belong to the placement’s owner), or to null for the
owner’s top level. Set category to any non-blank string (max 255
characters; leading and trailing whitespace is trimmed) or to null to
clear it — categories are free-text, there is no configured list to
match against. displayName lives on the file itself (one name
everywhere) — rename it via the file PATCH.
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
File identifier
Placement identifier
Body
Response
Placement updated
Id of the updated placement
The file the placement belongs to
The placement owner's entity type
The placement owner's entity id (null for the company level)
The folder the placement now sits in
The placement's category after the update
