YouTube Channel Live Scraper
A YouTube channel's live streams and past broadcasts as typed JSON: stream ID, title, watch URL, view count and length in seconds, plus the channel's ID and handle. 1 credit per call. No YouTube login, no proxies.
Free API key · 1 credit per page of streams · failed calls free
// GET /api/v2/youtube-channel-live/?channels=ishowspeed · sample from the catalog { "success": true, "data": { "channel": { "id": "UCWsDFcIhY2DBi3GB5uykGXA", "title": "IShowSpeed", "handle": "@IShowSpeed" }, "lives": [ { "id": "drXRrB4wFRg", "url": "https://www.youtube.com/watch?v=drXRrB4wFRg", "title": "BUYING THE NEW iPHONE 18!", "viewCountInt": 5700000, "lengthSeconds": 10109 } ], "next_cursor": "eyJjbSI6eyJpZCI6IlVDV3NERmNJaFkyREJpM0dCNXV5a0dYQSJ9LCJjdCI6IkNCUVNEWFYxWXktbGl2ZS10Li4uIiwiaCI6ImFiYzEyMyJ9" } }
| field | value | type | Has a value✓ |
|---|
Scrapier's YouTube Channel Live Scraper lists a channel's live streams and past broadcasts as JSON, a page at a time: id, title, url, viewCountInt and lengthSeconds, plus the channel object. It costs 1 credit per successful call. No YouTube login.
YouTube Channel Live Scraper extracts a channel's streams one page per call: stream ID, title, watch URL, view count as a number and length in seconds, along with the channel's ID, title and handle. Every response is structured JSON, ready to pass directly to an LLM, index into a vector store or feed a streamer-tracking pipeline. It is one of 17 YouTube endpoints on the same API key used by 12,000+ developers. Follow next_cursor to read older broadcasts.
What data can I extract with YouTube Channel Live Scraper?
Using this YouTube Channel Live Scraper, you can extract the following data from public YouTube pages of streams:
Want the exact field names? See the example output.
Try YouTube Channel Live Scraper Live
Press Run to see the catalog sample. Add your API key and it runs a real call to the Scrapier API from your browser. The key is sent only to proxy.scrapier.io and never stored.
+ Run live with your API key
How to use YouTube Channel Live Scraper
Hand it to your AI assistant, or run it yourself in five steps.
Copy to your AI assistant
Paste this into ChatGPT, Claude or Cursor and it knows how to call the scraper.
Use the Scrapier YouTube Channel Live Scraper to get public YouTube pages of streams. Endpoint: GET https://proxy.scrapier.io/api/v2/youtube-channel-live/?channels={channels} with header "X-API-Key: YOUR_API_KEY" and a 210-second timeout. Send one value per call in channels; for a list, make one call per value, at most 3 in parallel. It returns JSON under data.lives: id, url, title, viewCountInt, lengthSeconds. Each successful call costs 1 credit; failed calls are free. If you support MCP, run: claude mcp add -t http scrapier https://mcp.scrapier.io/mcp --header "X-API-Key: YOUR_API_KEY" and call run_scrape with endpoint "youtube-channel-live" (find it with search_endpoints).Use this scraper from ChatGPT, Claude or Cursor. Point your assistant at Scrapier and it reads YouTube pages of streams on its own: no glue code, no scraping logic in your prompts.
Run it yourself
- Get your free Scrapier API keySign up at app.scrapier.io; the free tier lets you try it first.
- Open YouTube Channel Live Scraper in the catalogIt lives under Scrapers / YouTube.
- Enter the channel handle, URL or IDFor example
ishowspeedinchannels, or a @handle, a channel URL or a channel ID. - Send your API requestOne GET with your key in the
X-API-Keyheader, or onerun_scrapecall from your agent. Set a 210-second client timeout. - Save your resultsEach page comes back as JSON in
data.lives: store it as is, or flatten it to CSV. Passdata.next_cursorback to read older streams.
How to scale to bulk YouTube pages of streams
channels takes one channel per call, so for a list of streamers you loop: one request per channel. Within a channel, pass back data.next_cursor to read older broadcasts. Run up to 3 requests in parallel per API key; above that the API answers 429 with a Retry-After header, and throttled calls cost nothing. Each page is 1 credit and failed calls are free, so 1,000 pages cost 1,000 credits, inside the Hobby plan's 15,000.
Features
YouTube Channel Live Scraper gives you a channel's streaming history as clean rows. It suits streamer research, live-event tracking, sponsorship checks and any workflow that needs stream titles, views and lengths from a channel's Live tab.
- Streams
id,titleandurlfor each live stream or past broadcast - Audience
viewCountIntas a number you can sort and chart - Length
lengthSecondsas a number of seconds - ChannelThe
channelobject withid,titleandhandle - Paging
next_cursorreads older broadcasts page by page
Proxies, retries and parsing run on Scrapier's side, so you send one request and get JSON back, at 1 credit per page of streams and 0 credits for a failed call.
Use cases
- Talent manager lists a streamer's past broadcasts with view counts and lengths to see which formats draw the biggest live audiences.
- Sponsorship analyst checks how often a creator streams and how long each stream runs before booking a sponsored live segment.
- Media researcher exports the stream history of 20 gaming channels into a dataset, one row per broadcast, for a study of live-content trends.
- Community manager polls a channel list daily and posts new stream titles and URLs to a team channel.
- AI engineer gives an agent a tool that lists a channel's recent streams, then passes each
urlto the video details endpoint for the full record.
Running these from an agent? Use the MCP integration and let Claude or Cursor call the scraper directly.
Why choose this Scraper API?
One endpoint covers a channel's live content, with view counts as numbers and lengths in seconds, so sorting needs no text parsing.
channels accepts a @handle, a channel URL or a channel ID (aliases channel and handle), and the response returns the channel object so you can match results to your list.
Channel, video and search endpoints share the same key and response envelope, so a stream URL feeds the next call without new code.
Input
The scraper takes one YouTube channel per call in channels: a @handle, a channel URL or a channel ID. It is required on the first call. Send parameters in the query string (GET) or as a JSON body (POST).
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
channels | string | Yes | — | A YouTube channel: @handle, channel URL or channel ID. One per call. Required on the first call. Aliases: channel, handle |
cursor | string | No | — | Pass back data.next_cursor from the previous response to get the next page; null means the last page |
use_proxy | boolean | No | true | Route through Scrapier's residential proxy pool. Leave as is |
raw_data | boolean | No | false | Return YouTube's raw upstream payload under raw_responses instead of the formatted items |
One channel per call: to scan ten channels, make ten calls and page each with cursor. Booleans are the strings true or false.
Example input
{
"channels": "ishowspeed",
"use_proxy": "true",
"raw_data": "false"
}Error codes
| Status | Meaning | Billed | Fix |
|---|---|---|---|
| 200 | Page of streams data returned in data.lives | Yes | — |
| 400 | Bad or missing input | No | Check channels: one value per call |
| 401 | X-API-Key header missing | No | Add the header |
| 402 | Out of credits (body has balance) | No | Top up; retrying will not help |
| 403 | Invalid or revoked API key | No | Check the key in your dashboard |
| 429 | Throttled | No | Wait Retry-After seconds, then retry |
| 5xx | Upstream failure or timeout | No | Retry with backoff; set a 210 s client timeout |
From the error reference. Any non-2xx response costs 0 credits.
Output
Typed JSON with the same schema on every call. One call returns a page of streams under lives, each with 5 fields, inside the standard data envelope. data.channel identifies the channel. Field names stay the same on every call. Set raw_data to true if you want YouTube's raw payload instead.
Example output
{
"success": true,
"data": {
"channel": {
"id": "UCWsDFcIhY2DBi3GB5uykGXA",
"title": "IShowSpeed",
"handle": "@IShowSpeed"
},
"lives": [
{
"id": "drXRrB4wFRg",
"url": "https://www.youtube.com/watch?v=drXRrB4wFRg",
"title": "BUYING THE NEW iPHONE 18!",
"viewCountInt": 5700000,
"lengthSeconds": 10109
}
],
"next_cursor": "eyJjbSI6eyJpZCI6IlVDV3NERmNJaFkyREJpM0dCNXV5a0dYQSJ9LCJjdCI6IkNCUVNEWFYxWXktbGl2ZS10Li4uIiwiaCI6ImFiYzEyMyJ9"
}
}The catalog's sample response for channels=ishowspeed, labelled as a sample: live calls return the account's current values.
Stream
| Field | Type | Example | Description |
|---|---|---|---|
lives.id | string | "drXRrB4wFRg" | YouTube video ID of the stream |
lives.title | string | "BUYING THE NEW iPHONE 18!" | Title of the stream |
lives.url | string | "https://www.youtube.com/watch?v=drXRrB4wFRg" | Watch URL of the stream |
Audience and length
| Field | Type | Example | Description |
|---|---|---|---|
lives.viewCountInt | integer | 5700000 | View count as a number |
lives.lengthSeconds | integer | 10109 | Length of the stream in seconds |
Response envelope and paging
| Field | Type | Example | Description |
|---|---|---|---|
success | boolean | true | true on every 200 response |
data.channel | object | {…} | The channel: id, title and handle |
data.next_cursor | string | "eyJjbSI6eyJpZCI6IlVDV3NERmNJaFkyREJpM0dCNXV…" | Pass back as cursor for older streams; null on the last page |
How does it work?
Scrapier sends each request through its residential proxy pool (use_proxy, on by default), so you never manage IPs or proxy accounts.
Retries and parsing of YouTube's pages and responses happen on Scrapier's side. You send one HTTP request and get typed JSON back.
Only publicly visible data is returned: what any visitor sees without signing in. No YouTube account, cookie or Google API key is used for this endpoint.
The schema is stable. When YouTube changes, Scrapier updates the scraper; the field names under lives stay the same.
How do you integrate YouTube Channel Live Scraper into your stack?
It works with what you already use: any HTTP client, AI agents over MCP, and no-code automation tools. Code samples for cURL, Python and Node.js are on the API tab.
MCP integration for AI agents
This registers the Scrapier MCP server, whose tools reach every Scrapier scraper, including youtube-channel-live: the agent finds it with search_endpoints and calls it with run_scrape. Works with Claude Code, Cursor and Windsurf. MCP calls are billed like REST: 1 credit per successful call. Full MCP setup →
No-code tools (n8n, Make, LangChain)
Use the HTTP Request node with your Scrapier API key in an X-API-Key header and point it at /api/v2/youtube-channel-live/ with a channels query parameter. Map data.lives into the next node.
Add an HTTP "Make a request" module with the same header and URL, and parse the response as JSON. Map title and viewCountInt straight into Sheets, Airtable or your CRM.
Wrap the endpoint in a requests-based tool, or load the Scrapier MCP server through LangChain's MCP adapters so the agent finds youtube-channel-live with search_endpoints itself.
Pricing and Rate Limits
One YouTube page of streams costs 1 credit, so 1,000 pages of streams cost 1,000 credits: $1.58 on the Pro plan. Failed and empty calls are not billed. Run up to 3 requests in parallel per key; above that the API answers 429 with a Retry-After header.
| Plan | Monthly price | Credits | Pages of streams included | Per 1,000 pages of streams |
|---|---|---|---|---|
| Hobby | $29 | 15,000 | 15,000 | $1.93 |
| Pro | $79 | 50,000 | 50,000 | $1.58 |
| Scale | $299 | 250,000 | 250,000 | $1.20 |
| Enterprise | Custom volume and terms | |||
Prices from the live billing page. See all plans and limits.
Call cost and timing
How we measure this
Credit cost, pagination and the sample come from the live catalog (GET /api/v2/endpoints, /youtube-channel-live/, checked 9 Nov 2026). Concurrency and timeout guidance come from the rate limits page of the docs. Scrapier does not publish latency or success-rate figures for this endpoint, so none are shown here.
YouTube Channel Live Scraper vs the Official YouTube API
| Feature | Scrapier page of streams scraper | Official YouTube API |
|---|---|---|
| Access needed | One Scrapier API key | A Google Cloud project, an API key and a daily quota |
| Which streams | Live streams and past broadcasts on any public channel | Live data through search and video resources, with separate calls to add details |
| Fields returned | 5 fields per stream: ID, title, URL, views and length | Depends on the resources and parts you request and combine |
| Rate limits | Up to 3 parallel requests per key; 429 with Retry-After | Daily quota units set per Google Cloud project |
| Setup | Sign up, copy a key, send a request | Create a project, enable the API, create credentials |
| Cost | 1 credit per page, from $1.20 per 1,000 pages | Free within quota; more needs a quota extension request |
The official YouTube Data API is the better choice when you manage the channel and need live chat or broadcast controls, which a public scraper does not provide.
Is it legal to scrape YouTube data?
Scraping publicly available YouTube data is generally lawful in many countries, but the answer depends on what you collect, where you are and how you use it. In the US, hiQ Labs v. LinkedIn is the case most often cited on public-data scraping. Scrapier returns only data any visitor can see without logging in. Under GDPR and similar laws, collecting public data can be permissible, but how you store and use personal data, such as names or comment text, must still comply with local data-protection rules, and YouTube's terms apply. Consult legal counsel if your use case involves bulk storage of personal data. This is not legal advice; see our Terms of Use.
Frequently asked questions
What fields does YouTube Channel Live Scraper return?
Each stream has id, title, url, viewCountInt and lengthSeconds, and data.channel gives the channel's id, title and handle: 5 fields per stream in data.lives. Each successful call costs 1 credit and needs no YouTube login.
Does it return streams that are live right now?
The catalog describes this endpoint as a channel's live streams and past broadcasts, with view count and length. The sample shows finished streams with a length in seconds. Check the lives array of your own call for what a given channel returns.
How do I read older streams?
Pass data.next_cursor back as cursor on the next call. Each page is one call at 1 credit, and a null next_cursor means you reached the end. Keep the channel input the same while you page.
Can I scrape the streams of multiple channels at once?
Yes, with one call per channel: channels takes a single value. Loop over your list and run up to 3 requests in parallel per API key. Failed and throttled calls are free.
Does YouTube Channel Live Scraper require a YouTube account or login?
No. The YouTube Channel Live Scraper uses no YouTube account or cookies: you send your Scrapier API key in the X-API-Key header and a channel handle, URL or ID, and get JSON back. Only public YouTube data is returned, and no Google API key or quota is involved.
How fast does YouTube Channel Live Scraper run?
Scrapier does not publish a latency figure for this endpoint. Each call reads YouTube live, and Set a client timeout of 210 seconds, as the docs recommend for every endpoint.
What happens if the input is wrong or YouTube returns nothing?
If a call fails, the API returns a non-2xx status and costs 0 credits. In code, check the status, then skip that input or retry it later. Throttled calls (429 with a Retry-After header) are free as well, so retry loops cost nothing.
Does YouTube Channel Live Scraper work with Claude, ChatGPT and other AI agent tools?
Yes. Connect the Scrapier MCP server with claude mcp add -t http scrapier https://mcp.scrapier.io/mcp and your API key in an X-API-Key header; it works in Claude Code, Cursor and Windsurf. The agent finds youtube-channel-live with search_endpoints and calls it with run_scrape. Any agent that can call an HTTP endpoint can use the REST API directly.
How does it compare to other YouTube scrapers?
Scrapier charges a flat 1 credit per successful call, and failed calls are free; platforms that bill compute units vary with run time and infrastructure. The same API key and MCP server reach all 199 Scrapier endpoints. Scrapier returns structured JSON for public YouTube data.
Does it return data in a format LLMs can use directly?
Yes. Every response is typed JSON with the same field names on every call: no HTML parsing and no selectors. Pass it straight to an LLM, index it into a vector store or return it from an agent tool.
What happens when YouTube changes its layout or anti-bot system?
Scrapier maintains the scraper. When YouTube changes its pages or internal responses, Scrapier updates it, and your calls keep returning the same JSON field names without changes on your end.
How much does it cost to run YouTube Channel Live Scraper 1,000 times?
1,000 credits, because each call is 1 credit. That is about $1.93 on Hobby, $1.58 on Pro and $1.20 on Scale, at the plans' price per credit. Failed calls are free.
How do I use YouTube Channel Live Scraper with Python?
Send a GET request with the requests library to https://proxy.scrapier.io/api/v2/youtube-channel-live/ with params={"channels": "ishowspeed"}, your key in the X-API-Key header and timeout=210. Read r.json()["data"]["lives"]: it is already JSON, so no HTML parsing is needed.
Is it legal to scrape YouTube data?
It depends on your use and your country, so this is not legal advice. Scrapier returns public YouTube data only. YouTube's terms and privacy law such as GDPR or CCPA apply to how you store and use it. Collect only what you need, and ask a lawyer about your specific case.
Your feedback
Found a bug or missing a field? Let us know. Write to support@scrapier.io and the team replies to every report.
Start Scraping YouTube Pages Of Streams
Public YouTube pages of streams as JSON, 1 credit each, from REST or MCP.