posts_get
One read: per-channel content with counted length and provider limit, `errors[]` and `warnings[]` with machine fixes, media readiness, approval state, and — after fan-out — each channel's publish result (`url`, `externa…
One read: per-channel content with counted length and provider limit, errors[] and warnings[] with machine fixes, media readiness, approval state, and — after fan-out — each channel’s publish result (url, external_post_id, or a sanitized error). Poll this after publishing; there is no separate status call. ready is the only publishability signal.
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 |
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 postsGet and the CLI command inklate posts get run the same guarded procedure the dashboard uses — same permissions, same validation, same tenant isolation.