manage public links
The workspace’s public links: pages anyone opens without an account. create builds one from chosen items and answers at once with link_url, live; a file that exists only on a computer is named back rather than placed. get returns the layout as blocks with a revision, and what visitors wrote. update takes blocks for a full rewrite, or only the fields that change; settings reach the live page at once, a layout change stays a draft until publish. Also list, activity, duplicate, unpublish, and delete, which removes the link and its activity for good, never the media; a file the link itself sent to the cloud returns to the computer holding it. Not indexed by search engines. 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
create, list, get, update, publish, unpublish, duplicate, delete, activity Link id, slug or title, required for everything but create and list. Slug and title are matched against the 100 most recent links; older ones need their id.
create: the items on the link, in order.
1 - 200 elementsAn item ref, item id, or the job id that made it.
create: the link's title. update: its new title. duplicate: the copy's title. The name it is filed under, not what the page says.
update: the heading the page carries, and the title a pasted link previews with. Null puts the link's own name back on the page.
update: issue a fresh link; the old one stops working. For revoking a link that leaked.
update: whether the link answers at all.
update: visitors can leave comments.
update: append these to the link's layout without touching the rest of it, live after the next publish. Audio joins the page's playlist when it has one with room; everything else lands in a gallery or file list.
An item ref, item id, or the job id that made it.
update: take these out of the layout; they leave the live link and its grant at the next publish.
An item ref, item id, or the job id that made it.
update: the whole layout, replacing what is there; get first and pass revision. Each block has a type and, to keep a block from get, its id: {type: "heading", level: 1|2|3, text}; {type: "text", text} (markdown); {type: "divider"}; {type: "items", items: [{ref, size?: "s"|"m"|"l", note?, download?, show_id?}], align?: "left"|"center"} (one picture stands alone, several become a gallery, audio a player, a CSV a table, the rest a download row); {type: "embed", url, note?} (YouTube, Vimeo, Loom, Figma, Spotify). A bad block is refused by its position.
300update with blocks: the revision from get. A stale one refuses rather than overwriting.
Optional: one sentence shown to the user beside this action.
600
