Edit, reschedule, or cancel a post
Change future work while protecting approvals, idempotency, and already-delivered targets.
PATCH a post to change caption, media, provider configurations, publish_at, or timezone while it remains editable. Use the cancel action for future dispatch. Material changes create a new revision and may return the post to review depending on brand policy.
What this means in practice
PATCH a post to change caption, media, provider configurations, publish_at, or timezone while it remains editable. Use the cancel action for future dispatch. Material changes create a new revision and may return the post to review depending on brand policy.
Use the documented brand and account boundaries consistently across the scheduler, REST API, SDK, MCP tools, SSE consumers, and webhooks. That makes the same social operation explainable to an operator and reproducible by an integration.
Implementation checklist
Fetch the latest post revision before editing.
Apply only the fields the user intentionally changed.
Preview again after content, media, target, or schedule changes.
Communicate whether approval remains valid or must be repeated.
Confirm target outcomes before promising that cancellation removed remote content.
Example request
This example uses a server-side API key and an explicit brand selection. Replace placeholder values and keep credentials out of browser bundles, client logs, and source control.
curl --request PATCH \
--url 'https://postapi.app9.co/v1/social-posts/POST_ID' \
--header 'Authorization: Bearer APP9_POST_API_KEY' \
--header 'X-App9-Post-Brand: BRAND_ID' \
--header 'Content-Type: application/json' \
--data '{
"caption": "Updated campaign copy.",
"publish_at": "2026-08-21T16:30:00Z",
"timezone": "America/New_York"
}'Operational details
Dates remain UTC in storage even when a user drags a calendar item in brand time.
A canceled future target can preserve its original schedule for audit purposes.
Remote deletion is capability-dependent and separate from canceling unpublished work.
Common mistakes to avoid
- Do not update a stale local copy without checking the current revision.
- Do not preserve approval after a material content change unless policy explicitly allows it.
- Do not describe local cancellation as remote deletion.