manage cards
Cards on a board or calendar: a title, a markdown body, attached library items and the workspace’s labels. A card lives on one board, between its columns, or one calendar, between its days, and is not a library item. list takes on (a board or calendar) and, for a calendar, from and to; read returns the body, attachments and revision; update and delete take card_id, and update needs if_revision from read. Deleting a card leaves its attachments in the library. 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 default: for a key or a connected agent, one of the workspaces the user allowed it.
Body
list, read, create, update, delete Board or calendar, by name or id. Required for list and create.
Required for read, update and delete.
Board column by name or id, or calendar day as YYYY-MM-DD. Required for create; on update, moves the card within its board or calendar.
Required for create.
1 - 200Markdown as in save_document, up to 20,000 characters. Empty clears it; omitted keeps it.
20000The complete ordered list of library refs or ids. Empty removes every one; omitted keeps them.
50The complete list of labels by name or id. Empty removes every one; omitted keeps them.
20update, on a board: the card's place in its column, top to bottom, lower first.
Calendar list: first day, YYYY-MM-DD.
Calendar list: last day, YYYY-MM-DD.
The revision from read. Required for update; a stale one refuses the write.
Optional: one sentence shown to the user beside this action.
600
