Skip to content

content_publications_validate

Dry run: check a post against one or more channels WITHOUT scheduling anything.

Tool

content_publications_validate

Dry run: check a post against one or more channels WITHOUT scheduling anything.

Dry run: check a post against one or more channels WITHOUT scheduling anything. Returns everything that would go wrong — text too long, media not stored yet, attachments a network will not take, a link it will not linkify — and what publishing would cost. On X a post carrying a link costs $0.20 against $0.015 for a plain one, so call this before you schedule.

Behavior

HTTP
POST /content/publications/validate

Arguments

NameTypeRequiredDescription
postIdstringThe post to check. It does not have to be approved yet — this never publishes.
channelsarrayOne entry per channel you are considering. Check them all in one call.
scheduledAtstringThe slot you intend to use, ISO-8601. Only the daily ceiling depends on it; omit for "now".

Response

FieldTypeAlwaysDescription
postIdstringThe post that was checked.
channelsarrayOne result per requested channel, in the order they were given.

Try it

Dry run: check a post against one or more channels WITHOUT scheduling anything.

When to use

Dry run: check a post against one or more channels WITHOUT scheduling anything. Returns everything that would go wrong — text too long, media not stored yet, attachments a network will not take, a link it will not linkify — and what publishing would cost. On X a post carrying a link costs $0.20 against $0.015 for a plain one, so call this before you schedule.

Example

Ask your agent something like this:

Dry run: check a post against one or more channels WITHOUT scheduling anything.

The agent will invoke content_publications_validate with these arguments:

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

Esc

Start typing to search the docs.

navigateselect