Skip to content

content_posts_move

Move a post in any status into a folder, before another post there, or out to the unfiled plan.

Tool

content_posts_move

Move a post in any status into a folder, before another post there, or out to the unfiled plan.

Move a post in any status into a folder, before another post there, or out to the unfiled plan. This changes only plan order, never approval or content version. The destination must belong to this product.

Behavior

HTTP
POST /content/posts/:postId/move

Arguments

Name
Type
Required
Description
postId
string
•
The post id returned by content_posts_create.
folderId
string
•
Destination folder in this product, or null to leave the post unfiled.
beforePostId
string
—
Put the post immediately before this post in the destination folder. Omit to append it.

Response

Field
Type
Always
Description
id
string
•
Post id.
text
string
•
The current text of the post, in markdown.
media
array
•
Media references attached to the current version.
notes
string
•
Private plan notes, or null when unset.
title
string
•
Plan title, or null when unset.
author
string
•
Identity id of whoever composed the post.
status
string
•
Post lifecycle status: idea (may have no text) -> draft (being written) -> pending_approval (submitted) -> approved (cleared to publish). Past approval the status follows EVERY output of the approved version (see outputs): scheduled while an output is queued or in flight and none is out yet; partially_published once some outputs are out and others are still queued, failed or never scheduled; published once every output is out; failed when an output gave up and none is out or queued; back to approved when nothing is live any more (all cancelled). A post in any of these five statuses can still have an output scheduled, including a failed one again.
outputs
array
•
One entry per output of this post, in targets order, with the state its publications add up to and the publication that decides it. Before approval every output is `none`. The post's status past approval is derived from exactly these states.
targets
array
•
The outputs of this post — a network and a variant each; several may share a network.
folderId
string
•
Folder containing this post, or null.
position
integer
•
Order within its folder, or null for an unfiled post.
createdAt
string
•
ISO-8601 creation time.
updatedAt
string
•
ISO-8601 time of the last change.
currentVersion
integer
•
Version number of the current text.
approvedVersion
integer
•
The version an approval binds to, or null. Cleared on every edit: approving one text never covers another.

Try it

Move a post in any status into a folder, before another post there, or out to the unfiled plan.

When to use

Move a post in any status into a folder, before another post there, or out to the unfiled plan. This changes only plan order, never approval or content version. The destination must belong to this product.

Example

Ask your agent something like this:

Move a post in any status into a folder, before another post there, or out to the unfiled plan.

The agent will invoke content_posts_move with these arguments:

{
  "postId": "<postId>",
  "folderId": "<folderId>"
}

Esc

Start typing to search the docs.

↑↓navigate↵select