Twitch Scraper — Channels, Live & VODs | from $1.50/1K | No Auth Required

For gaming market researchers, influencer marketing platforms, and gaming-industry analytics teams that need Twitch data at scale.

Pricing: $1.50 per 1,000 channels · $2.50 per 1,000 VODs (when includeVideos=true)

Scrape Twitch channel profiles, live stream data, and VOD archives via the official public Twitch GraphQL API. No user authentication required. Pay per result.

Pricing example

$1.50 per 1,000 channel records · $2.50 per 1,000 VODs (when includeVideos=true). Example: 50 channels = $0.08. 50 channels + 20 VODs each = $0.08 + $2.50 = $2.58. No per-run fee. No auth required.

Sample output

{
  "type": "channel",
  "channel_login": "shroud",
  "display_name": "shroud",
  "followers": 11240000,
  "is_live": false,
  "stream_title": null,
  "game": null,
  "viewers": null,
  "last_broadcast_title": "TACTICAL SHOOTER MARATHON",
  "is_affiliate": false,
  "is_partner": true,
  "created_at": "2014-04-25T00:00:00Z",
  "parse_confidence": 1.0,
  "scraped_at": "2026-06-05T09:00:00Z"
}

What you get

For each channel:

• Followers count — total followers
• Live status — is the channel currently live?
• Stream details — title, game/category, viewer count, start time, tags
• Channel metadata — description, partner/affiliate status, profile image, account creation date
• Last broadcast — title and start time of the most recent stream

Optional per-channel:

• VOD archive — recent past broadcasts with title, view count, duration, game, thumbnail URL

Use cases

• Gaming market research — track which games are trending by viewer count
• Influencer monitoring — monitor follower growth and live status for lists of streamers
• Content analytics — analyse VOD performance (views, duration, games)
• Competitive intelligence — benchmark streamers by category or game
• Data feeds — build live gaming dashboards with fresh Twitch data

Input

Field	Type	Default	Description
channels	string[]	["shroud", "pokimane", "ninja"]	Twitch login names to scrape
maxItems	integer	100	Max total items to push (0 = unlimited)
includeVideos	boolean	false	Also fetch VOD archive per channel
maxVideosPerChannel	integer	20	Max VODs per channel (1–100)

Output schema

Each dataset row has type = "channel" or "video".

Channel row fields: channel_id, channel_login, display_name, description, followers, is_live, stream_title, game, game_id, viewers, stream_started_at, stream_tags, last_broadcast_title, last_broadcast_at, is_affiliate, is_partner, profile_image, created_at, scraped_at, parse_confidence, warnings

Video row fields: channel_id, channel_login, display_name, video_id, video_title, video_views, video_duration_s, video_status, video_game, video_thumbnail, published_at, created_at, scraped_at, parse_confidence, warnings

Frequently asked questions

Do I need a Twitch account or API key? No. The actor uses the same public GraphQL endpoint Twitch's own website calls, with the standard web Client-ID. No signup, no developer app, no OAuth required.

Do I need a proxy? No. The Twitch public GraphQL API is open to datacenter IPs. No proxy cost to you.

What formats does output come in? JSON, CSV, Excel via the Apify dataset. Native integration with n8n, Make, Zapier.

What if a channel returns empty or is not found? The actor logs channel_not_found and continues to the next channel in the list — no crash, no charge for the missing channel.

Technical notes

• Uses the official Twitch public web GraphQL endpoint (gql.twitch.tv/gql) with the standard public web Client-ID — no API key signup required.
• Videos: fetches up to 100 VODs per channel in a single request (no pagination needed for most use cases).
• parse_confidence (0.0–1.0) and warnings in every row provide machine-readable quality signals.

Pricing

$1.50 per 1,000 channel records · $2.50 per 1,000 VOD records (when includeVideos=true). PPE — pay per result, no per-run fee. No auth required.

Why this Twitch scraper beats the alternatives

	This scraper	epctex/twitch-scraper	Generic API wrappers
Price	$1.50/1K channels	~$3-5/1K	varies
VOD archive (separate event)	$2.50/1K	included flat	✗
Official Twitch GraphQL API	✓	partial	✓
No user OAuth required	✓	✓	✓
Live stream + game + viewer count	✓	partial	partial
parse_confidence on every record	✓	✗	✗

Live monitoring use case

Run on a schedule to track live status for a list of gaming influencers — get followers, viewer counts, and current game on every run. Set includeVideos=false for lightweight live-status checks, or includeVideos=true for full VOD analytics.

Use with AI Agents (MCP)

This Twitch scraper is callable as a tool by AI agents (Claude Desktop, Cursor, VS Code, n8n, or any MCP-compatible client) via Apify's hosted Model Context Protocol server.

{
  "mcpServers": {
    "apify": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.apify.com/?tools=bovi/twitch-scraper",
        "--header",
        "Authorization: Bearer <YOUR_APIFY_TOKEN>"
      ]
    }
  }
}

Integrations

Built for gaming market researchers and influencer-marketing platforms benchmarking channel reach, live status, and VOD archives — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Douyin Scraper
• Maigret Username Osint
• Patreon Scraper
• Pinterest Scraper
• Reddit Scraper
• Social Media Finder

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.