YouTube API

YouTube Channel lives API

List a YouTube channel's live and past-live streams by handle or channel ID with cursor pagination (title, views, length, publish time).

$1.20/1k req, pay per request, no subscription.

What the API returnedlives[0]
{
"id": "kQ7mZ2vT8pL",
"url": "https://www.youtube.com/watch?v=kQ7mZ2vT8pL",
"title": "RANKED GRIND to Diamond - road to top 500 !builds !coach",
"views": 3140,
"lengthText": "3:12:08",
"publishedTime": "Streamed 4 hours ago",
"image": "https://i.ytimg.com/vi/kQ7mZ2vT8pL/hqdefault.jpg"
}
Uptime
100.00%
30d · 512 calls
Requests
512
30d · weekly, last 12 wks
Response
1.1s
median · 30d

Pricing and providers

YouTube Channel lives API pricing: one API, 2 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$12.00
$1.20/1k req, only for what you use. No monthly plan.
Your first 83 requests are free with the $0.10 starting balance.

Try it

Get YouTube channel lives in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `lengthText`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a live stream that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 11 of 12 fields. See every field

{
  "found": true,
  "data": {
    "nextCursor": "Eg0SC1BpeGVsZm9yZ2UxQoABAQ",
    "lives": [
      {
        "id": "kQ7mZ2vT8pL",
        "url": "https://www.youtube.com/watch?v=kQ7mZ2vT8pL",
        "title": "RANKED GRIND to Diamond - road to top 500 !builds !coach",
        "views": 3140,
        "lengthText": "3:12:08",
        "publishedTime": "Streamed 4 hours ago",
        "image": "https://i.ytimg.com/vi/kQ7mZ2vT8pL/hqdefault.jpg"
      },
      {
        "id": "nR4wY9uX2sK",
        "url": "https://www.youtube.com/watch?v=nR4wY9uX2sK",
        "title": "Sunday chill stream - new patch reactions and viewer games",
        "views": 8720,
        "lengthText": "2:45:51",
        "publishedTime": "Streamed 3 days ago",
        "image": "https://i.ytimg.com/vi/nR4wY9uX2sK/hqdefault.jpg"
      },
      {
        "id": "vB1cD6eF3gH",
        "url": "https://www.youtube.com/watch?v=vB1cD6eF3gH",
        "title": "Charity marathon for local food bank - 12 hour stream",
        "views": 15600,
        "lengthText": "12:03:44",
        "publishedTime": "Streamed 2 weeks ago",
        "image": "https://i.ytimg.com/vi/vB1cD6eF3gH/hqdefault.jpg"
      }
    ]
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • channelIdstring

    YouTube channel ID.

  • cursorstring

    Continuation token from a previous response for pagination.

  • handlestring

    @pixelforgegg

    YouTube channel handle.

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `lengthText`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a live stream that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

each livedata.lives[]

Populated whenever the provider has data for the entity.

  • idstring

    kQ7mZ2vT8pL

    Populated whenever the provider has data for the entity.

  • imagestring

    https://i.ytimg.com/vi/kQ7mZ2vT8pL/hqdefault.jpg

    URL of the live stream thumbnail image, tracking query parameters stripped.

  • lengthTextstringcan require

    3:12:08

    Stream length as YouTube shows it, such as 3:29:31, or LIVE while it is streaming; null when the serving source does not report it.

  • publishedTimestring

    Streamed 4 hours ago

    Populated whenever the provider has data for the entity.

  • titlestring

    RANKED GRIND to Diamond - road to top 500 !builds !coach

    Populated whenever the provider has data for the entity.

  • urlstring

    https://www.youtube.com/watch?v=kQ7mZ2vT8pL

    Populated whenever the provider has data for the entity.

  • viewsinteger

    3140

    Views of a past stream, or people watching a stream that is live now. Every source reads it from YouTube's rounded label ("60K watching" is 60000), so it is approximate.

datadata
  • nextCursorstring

    Eg0SC1BpeGVsZm9yZ2UxQoABAQ

    Opaque cursor for the next page of live streams, or null when this lane has no more. Pass it back as cursor to continue.

top level
  • foundboolean

    true

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the YouTube Channel lives API

The AnyAPI YouTube Channel lives API returns YouTube channel lives data as normalized JSON from one POST call to /v1/run/youtube.channel_lives. List a YouTube channel's live and past-live streams by handle or channel ID with cursor pagination (title, views, length, publish time). AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of YouTube channel lives calls through AnyAPI succeeded, with a median response time of 1.1 seconds across 512 measured calls.

It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

List a YouTube channel's live and past-live streams by handle or channel ID with cursor pagination (title, views, length, publish time). The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of YouTube channel lives calls through AnyAPI succeeded, with a median response time of 1.1 seconds across 512 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 83 YouTube Channel lives calls at $0.0012 each.

AnyAPI asks the next of its 2 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/youtube.channel_lives with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.