Tools

posts_update

Re-validates and returns the same response as posts_create.

Re-validates and returns the same response as posts_create. A scheduled_at time (re)books the post, “now” publishes it, null returns it to draft. per_channel overrides one channel’s copy, format, or options without touching the others — its content takes markdown, so per_channel: {"x": {"content": "shorter text"}} is the whole edit. per_channel: {"x": null} resets that channel to the shared content. Optimistic concurrency via expected_updated_at. The response carries per-channel validation: each channel entry’s errors[] name a code, the field to change, a human message with the real numbers, and a machine fix where one exists. ready is the server’s ONLY publishability signal — a draft with errors saves fine; only arming refuses. autofix (default true) applies suggested fixes server-side and reports them in fixes_applied.

Input

FieldTypeRequiredDescription
organizationstringnoOrganization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization.
idstringyesPost id
contentstringnoThe shared copy as markdown: **bold**, *italic*, [label](url), # heading, - bullet, blank lines between paragraphs. Markdown that contains no markup is posted exactly as typed — handles, URLs, and snake_case are safe — and \* shows a literal delimiter. Each channel’s copy is adapted from this unless per_channel overrides it. Optional only for a media-only post.
channelsarraynoTarget channels: channel ids from channels_list and/or provider names (“x”, “linkedin”), mixed. On update, when present it REPLACES the target set. A post response’s channels[] entries are accepted as-is.
per_channelobjectnoPer-channel overrides keyed by channel id or provider name. A non-null value also ADDS that channel to the targets; on update, a null value ({“x”: null}) resets that channel to the shared content. Overriding one channel never touches the others.
scheduled_atanynoReschedule intent. A future instant (ISO-8601 with offset, or “30m”/“2h”/“3d”/“1w”) (re)books the post; “now” publishes it immediately; null unschedules it back to draft; omitted leaves the schedule alone.
autofixbooleannoApply suggested machine fixes server-side before the verdict (default true). Applied fixes are reported in fixes_applied and mark that channel’s copy authored.
mediaarraynoOrdered media to attach, in render order: file ids (file_…) from files_upload and/or public https:// URLs (fetched and stored server-side — the response echoes each url’s file id; poll files_get until ready before publishing). Each target channel must support the media (see capabilities.media). A post response’s media[] entries are accepted as-is.
labelsarraynoLabel ids to set on the post — replaces the full set when present. A post response’s labels[] entries are accepted as-is.
campaignanynoCampaign id to file the post under; null detaches it.
expected_updated_atstringnoThe updated_at you last saw. When the post moved on since, the call is refused (409) instead of acting on someone else’s concurrent edit. Omit for last-write-wins.
idempotency_keystringnoClient-chosen dedupe key. Retrying with the same key returns the original result instead of creating/publishing twice. Pick one per logical action.

Set idempotency_key on retries: a repeated call with the same key returns the original result instead of acting twice. Use it whenever you cannot tell whether a timed-out call landed.

Result

JSON on success. A refusal comes back as an error prefixed with its code (NOT_FOUND, FORBIDDEN, TOO_MANY_REQUESTS, …) and a message written to be acted on — read it before retrying.

The same operation elsewhere

This tool and the REST operation postsUpdate and the CLI command inklate posts update run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.