manage boards
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
list, get, create, update, delete Board name or id, required for get, update and delete.
The word "delete", to delete the board named with its columns and every card's place on them. Permanent; the answer says what went; the items stay.
"delete"get: how many cards to read, up to 500. The whole board when left out.
get: next_cursor from the read before, with the same board.
The board's name (create), or its new name (update). Renaming the board renames the field, and the cards keep their columns.
What this board is for (create or update): the line another agent reads to tell two boards apart.
Lay out columns left to right. On create this is the whole board; on update they are appended, and a name already on the board is skipped rather than duplicated.
update: rename, recolor or set the limit on a column. Its cards keep their place in it.
update: column names or ids in the order they should read left to right. Any left out keep their order behind them.
update: remove these columns. Whatever sat in them comes OFF the board, since a column is what membership means; the items stay in the library.
update: the vertical order inside a column, the order a user sets by dragging. A named card sitting elsewhere is skipped, not moved; changing columns is update_items.
Optional: one sentence shown to the user beside this action.
600
