content_schedule_get

Read the complete publication-schedule history for one content post or series.

Read the shared content contract for authorization, app identity, result interpretation and recovery.

Inputs and scope

Require channelCode, pAppCode and target:{model,id}. model is POST or SERIES; id is the positive post/series ID, not an episode ID or task ID. Discover it through content_posts_get or content_series_get.

POST supports timeline, notice, free-board, article, photobook and resource families. SERIES supports articles, photobooks and resources. Question, inquiry, outlink and welcome scheduling are unsupported. Use the exact installed alias when applicable.

Results

CONTENT_SCHEDULES returns target, schedules, revision and target isPublished. It requires the complete schedule inventory, up to 100 historical tasks, with distinct numeric id and opaque taskId identities, matching target and submitter channel. Partial or malformed history is refused. There is no caller pagination argument.

Source scheduledAt values are UTC without a suffix. Mutation input requires an explicit offset; do not interpret the source string as the agent's local timezone. Read this revision immediately before content_schedule_apply. Choose the schedule's opaque taskId for replace/cancel, not its numeric id or the bridge's recovery taskId. Read-only inspection creates no journal and does not prove that a scheduled action will execute or notify anyone.

Input example

This is an input illustration, not a recorded call. Replace the channel, app, observed IDs and all-zero revision with values from the matching authorized read. A dry run does not save changes.

{
  "channelCode": "selected-channel",
  "pAppCode": "B00001",
  "target": {
    "model": "POST",
    "id": 1
  }
}