Skip to content

content_posts_attach_media

Attach stored media assets to a post, appended in the given order.

Tool

content_posts_attach_media

Attach stored media assets to a post, appended in the given order.

Attach stored media assets to a post, appended in the given order. Only assets that are ready can be attached. This counts as an edit: the post gets a new version and an approved post returns to pending_approval.

Behavior

HTTP
POST /content/posts/:id/media/attach

Arguments

NameTypeRequiredDescription
idstringThe post id.
mediaIdsarrayMedia asset ids, in the order they should appear on the post.

Response

FieldTypeAlwaysDescription
idstringPost id.
textstringThe current text of the post, in markdown.
mediaarrayMedia references attached to the current version.
authorstringIdentity id of whoever composed the post.
statusstringPost lifecycle status: draft (being written) -> pending_approval (submitted) -> approved (cleared to publish); scheduled/published/failed are set by the publishing pipeline.
createdAtstringISO-8601 creation time.
updatedAtstringISO-8601 time of the last change.
currentVersionintegerVersion number of the current text.
approvedVersionintegerThe version an approval binds to, or null. Cleared on every edit: approving one text never covers another.

Try it

Attach stored media assets to a post, appended in the given order.

When to use

Attach stored media assets to a post, appended in the given order. Only assets that are ready can be attached. This counts as an edit: the post gets a new version and an approved post returns to pending_approval.

Example

Ask your agent something like this:

Attach stored media assets to a post, appended in the given order.

The agent will invoke content_posts_attach_media with these arguments:

{
  "id": "<id>",
  "mediaIds": "<mediaIds>"
}

Esc

Start typing to search the docs.

navigateselect