media_uploads_get

# media_uploads_get

Read recent encoding candidates after the human uploads a video in the original console. It does not accept a file or initiate upload, registration or encoding.

The central server routes this reader to get and [media_upload_handoff](media_upload_handoff.md) explicitly to handoff; returning a destination does not fetch candidates.

## Inputs

Provide channelCode and exact pAppCode (`C00001`, `C00002`, `C00006`, `C00007`, `C00015`). The only view is candidates; it defaults to page 1/limit 15. query accepts page 1–10000 and limit 15/30/50/100.

The asset view has been removed. No assetId, file, bytes, path, URL, credential or upload grant is accepted. Use only the returned/authorized original-console destination for the human upload. VOD host staging is no longer an incoming prerequisite to this reader; file selection and transfer belong to the console.

## Result and interpretation

MEDIA_UPLOAD_CANDIDATES returns candidates, pagination, historyDays 10, postIdentityVerified false, playbackVerified false and writesPerformed false. Public candidate fields include candidateId, title, observed status, durationSeconds and fileSizeKb. States are WAITING, POSTED, FAIL or UNKNOWN. Sensitive storage payloads and credentials are not returned. The adapter verifies pagination and selected app consumer; one page is not the complete history.

Inspect the actual post separately with [media_posts_get](media_posts_get.md) when its identity is known. Do not adopt a post by title/filename alone. A missing candidate outside the ten-day history cannot establish that a prior upload never happened.

## Existing upload tasks

Old media-upload status/resume paths preserve observation only. Prepared or acknowledged old checkpoints cannot be continued by repeating apply; direct apply is retired. Post-sent recovery matches its exact issued object and expected metadata within a bounded scan of at most 5000 candidates. Preserve uncertain task IDs and inspect their outcomes before another human upload. The candidate reader creates no task and grants no retry, cleanup or restoration authority.

## Input example

Replace the selectors with the authorized installed target. This is a read only, not an upload example.

```json
{
  "channelCode": "selected-channel",
  "pAppCode": "C00002",
  "view": {"kind": "candidates", "query": {"page": 1, "limit": 15}}
}
```