Skip to main content
POST
Move workspace items in bulk
Move up to 100 workspace items — workbooks, reports, and folders, mixed freely — into one destination folder in a single request. Request body:
  • items — the items to move, each { type, id } with type one of WORKBOOK, REPORT, FOLDER. Repeated references to the same item are collapsed, so the response holds exactly one entry per distinct item requested.
  • folderId — the destination folder id for the whole batch, or null to move the items to the workspace root. For a folder item this becomes its new parent.
This endpoint is partially successful. It returns 200 whenever the request itself is well formed, and reports each item’s outcome separately:
  • moved — the items that were moved, serialized exactly as POST /workspace/move returns them.
  • failed — the items that were not moved, each with the (type, id) requested and an error carrying the status and message the single-item move would have returned for it (403 when the caller lacks access, 404 when the item does not exist or belongs to another deployment, 400 for an invalid move such as a folder into its own descendant).
An empty failed array means the whole batch applied. Items are applied one at a time in the order given, each in its own transaction, so earlier moves are not rolled back when a later item fails — the response is the record of what was applied. Access is checked per item with the same rules as the single-item move, so a batch mixing items the caller may and may not move applies the permitted ones and reports the rest.

Authorizations

Authorization
string
header
required

Token authentication. Send Authorization: Bearer <YOUR_TOKEN>.

Path Parameters

deploymentId
number
required

Body

application/json

BulkMoveWorkspaceObjectsInput

items
object[]
required
Required array length: 1 - 100 elements
folderId
integer | null

Response

200 - application/json
failed
object[]
required
moved
object[]
required