posts_delete
Remove the post's record, its history, and its metrics.
Remove the post’s record, its history, and its metrics. With takedown: true the provider-side copies are best-effort deleted FIRST — a provider with no delete API (see capabilities.takedown on the channel) keeps its copy live, so say so rather than claiming success. Without the flag, published posts stay live on the platforms; there is no record left afterwards of what to take down. Irreversible.
Input
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | no | Organization slug to act in (see organizations_list). Optional: API keys are bound to one organization; OAuth connections default to your active organization. |
id | string | yes | Post id |
takedown | boolean | no | Also best-effort delete the live provider-side copies before removing the record. |
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 postsDelete and the CLI command inklate posts delete run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.