youtube/channel/shorts — the channel's shorts, listed without counters

The call

Parameters (1)

That list is the whole list, and anything else is ignored in silence. An undeclared parameter is not rejected — it produces no error, no warning and no filtering. Check a parameter against this table before assuming a narrower result came back.

What the parameter list does not tell you

SHORTS ARE A SEPARATE SHELF, and the platform treats them that way: they do not come back from `youtube/channel/videos`, so a channel that posts both needs both routes. A real call on 4 October 2026 returned 48 items for one channel.

⚠️ `metrics` IS `{}` ON EVERY ITEM, AND `published_at` IS NULL. Both were measured on that call, on all 48 items, and neither is a parsing failure: the Shorts listing upstream simply does not carry counters or dates. Four of these twelve routes have an empty `metrics` for the same kind of reason, and in every one of them it means the same thing — WE DID NOT READ IT, not NOBODY DID IT. A `0` here would be a number we never measured.

SO ORDERING IS NOT AVAILABLE FROM THIS ROUTE. With no `published_at` you cannot sort by recency and you cannot ask 'what did this channel post this week' — the items arrive in the upstream's order and nothing in the response dates them. If you need the date or the counters for a Short, take its id from here and ask `youtube/video`, which answers both exactly. That is two calls, and the second one is the only one that can honestly produce a number.

Measured caveats (1)

Why there is no success body on this page

The 200 body for this endpoint is not transcribed here. Reading it needs a client key, and there is no client key on the machine these pages were built from — internal keys exist only as hashes, by design. An example we never received would look exactly like one we did, so instead of composing one, the response shape is documented field by field on the schema pages below. Those are generated from the contract and tested against it in both directions; an invented example would be tested by nothing.

Response shapes (4)

• PostItem — The normalised post shape. `metrics` carries likes, replies, reposts and quotes — and nothing else, because nothing else exists on every platform we read.
• PostsEnvelope — Every posts endpoint answers with this envelope. Eight fields, all required: you can read `success` and `credits_used` without checking whether they came.
• Author — The normalised profile shape, identical across all platforms. All twelve fields are nullable, and that is the design: a field we cannot read comes back null, never 0, because a zero would be a claim about the account.
• ApiError — Every 4xx and 5xx from the API carries this object. The `error` value is a stable string you can branch on; the extra fields appear only for the errors that have something to report.

Error codes (8)

Every one of them carries the same body shape: ApiError. The error value is a stable string you can branch on — branch on that, never on the message text.

400 · 401 · 402 · 404 · 405 · 451 · 503 · 502

Machine-readable

This endpoint is in /openapi.json (OpenAPI 3.1), with its cost on the operation itself. If you are generating a client, use the spec rather than this page — and note that the spec is filtered by what is switched on right now, so it is the better answer to "can I call this today".