media_schedules_get

# media_schedules_get

Read scheduled-publication records for a selected media post or collection without scheduling anything.

## Inputs

Provide channelCode, exact pAppCode (`C00001`, `C00002`, `C00006`, `C00007`, `C00015`), targetModel (`POST` or `SERIES`) and positive integer targetId. Shorts does not support SERIES. These are top-level fields, not a nested target object. A collection uses its series ID; a post uses its post ID, not an episode or VOD ID.

## Result and next step

`MEDIA_PUBLICATION_SCHEDULES` returns target, scheduledTasks, revision, `writesPerformed:false` and `publicationExecutionVerified:false`. The target and tasks must match the selected consumer, model, ID and submitting channel. The adapter requires complete task history within its 1000-entry bound; a partial first page or duplicate task identity fails verification.

Tasks contain both numeric record IDs and opaque taskId, publication manifest, target, scheduledAt, isFired, isCompleted and deactivatedAt. Use the observed taskId for replacement/cancellation in [media_schedule_apply](media_schedule_apply.md). This upstream ID is different from the bridge requestId/taskId used for recovery. Only active publication tasks for this exact target are editable; this reader does not make coaching-alert tasks editable. A saved schedule or an isFired field alone does not verify the eventual publication or visitor-visible result.

Read the [media workflow guide](../guides/media-workflows.md) for authorization, source-versus-runtime availability and common recovery rules.

## Input example

Illustrative input only. Replace the channel, installed app, identifiers and revision with values obtained for the selected target.

```json
{
  "channelCode": "selected-channel",
  "pAppCode": "C00002",
  "targetModel": "POST",
  "targetId": 1
}
```