inklate posts update

Change anything — content, channels, media, labels, campaign, or the schedule

Change anything — content, channels, media, labels, campaign, or the schedule

inklate posts update <id> [flags]

Arguments

ArgumentDescription
idPost id

Flags

FlagDescription
--content <value>New copy as markdown (replaces the current copy)
--channel <value>Repeatable: channel id or provider name — REPLACES the target set (repeatable)
--scheduled-at <value>(Re)schedule: “now”, ISO-8601 with offset, or “30m”/“2h”/“3d”/“1w”
--clear-scheduleReturn the post to draft
--per-channel <value>Per-channel overrides as JSON; content takes markdown; {“x”: null} resets that channel to the shared content
--autofixApply suggested machine fixes server-side (—no-autofix to disable)
--media <value>File ids, https URLs, or local paths (repeatable)
--label <value>Repeatable: replace the post’s labels (repeatable)
--campaign <value>Campaign id to attach
--detach-campaignDetach the post from its campaign
--expected-updated-at <value>Optimistic-concurrency guard from the last read
--idempotency-key <value>Dedupe key: retries replay, not duplicate

Output

Structured YAML on stdout (--json for JSON); progress and errors on stderr. Exit codes: 0 ok · 1 unexpected · 2 usage · 3 auth · 4 refusal · 5 not found · 6 conflict · 7 rate limited.

Global flags on every command: --org, --profile, --json, --quiet, --yes, --no-input, --base-url — see the CLI overview.

This command is a thin client over the REST API operation(s): postsUpdate.