organize items
Library structure in one batch: create, rename, describe, move and delete folders, move items into folders, label and unlabel, star, hide, rename and delete labels, group variations, stack versions, and create typed fields. Parts run in a fixed order, folders and labels made before anything is filed or labelled, so one call can create a path and move into it; create_folders takes whole paths and makes every missing segment. A folder is where an item is filed, a label is a workspace-wide mark people filter by, a tag (update_items) is a searchable word on the item, a field is a typed value. group_variations makes items peers of one concept, all visible; stack_versions folds one behind another so the library shows the current one. A board is a field, so moving a card is update_items. Each entry stands alone: the response says what every operation changed and skipped, and failed names the ones that did not run. Free.
Authorizations
An API key (es_live_…) from Settings, under API keys, or an OAuth access token.
Headers
Retry a paid dispatch safely: the same key returns the job already dispatched instead of charging again.
The workspace this one call acts in, when it is not the key's own.
Body
Take a label off these items. The label itself stays, on everything else that carries it.
Take items off the feed, or put them back. Nothing else changes: the files, their folders and every search are untouched, and search_library with hidden: true finds them again.
Rename in place; everything inside moves with it.
Say what a folder is for, in a line. It comes back with the folder everywhere it is read, so the next session opens the job already knowing it. Empty text clears it.
Rename or recolor a label. Items keep it; the assignment rides on the label, not its wording.
Delete a label. It comes off every item that carried it; no item is deleted or changed otherwise.
Label name or id.
Reparent a folder; everything inside comes with it.
Delete a folder and the folders inside it. Nothing filed in them is deleted; every item moves to the top level, and the response says how many.
Folder path or id.
Each entry groups its refs as one variation set (peers, no parent). To add items to an existing set, include any current member, and the sets merge.
Remove these items from their variation sets.
An item ref, item id, or the job id that made it.
Stack an item as a version of another: v2 of a cut, a re-render, a corrected export. A stack shows one item with its history behind it, where a variation set shows every peer side by side.
Take these out of their version stack; each stands on its own again.
An item ref, item id, or the job id that made it.
Make each of these the version its stack shows.
An item ref, item id, or the job id that made it.
Create typed columns on the workspace. A date field is what a calendar view reads, a select is what a board reads. update_items sets values by name and refuses a name that does not exist, so the field is made here first.
Optional: one sentence shown to the user beside this action.
600