Resolve any public Twitch channel into structured JSON — live status, current viewers, category and title, follower totals, plus VOD and clip metadata — refreshed as often as you need.
Twitch is the dominant live-streaming platform for gaming, IRL, and creative broadcasts, where channel state changes minute to minute. The Twitch Scraper API captures public channel pages, directory listings, VOD archives, and clip galleries, returning a typed snapshot of who is live, what they are playing, and how many people are watching.
Esports analysts, sponsorship agencies, and game studios use it to track streamer reach and category momentum without polling fragile internal endpoints. Every field — concurrent viewers, stream uptime, game category, clip view counts — comes from public surfaces and is normalized for time-series storage.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.twitch.com/",
"type": "profile",
"include": "recent_posts"
}'
// ← response
{
"status": "ok",
"data": {
"username": "...",
"followers": 1840221,
"posts": 412,
"verified": true,
"recent_posts": [
{ "id": "…", "likes": 21044, "comments": 882 }
]
}
}Twitch data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Live streamer and viewership tracking
Esports and tournament audience analytics
Influencer sponsorship valuation
Game category trend monitoring
Yes. Poll a channel on your schedule and we return its current live state, concurrent viewer count, active category, and stream title so you can trigger alerts the moment a broadcast starts.
We extract public clip and VOD listings with titles, durations, view counts, creator, and timestamps so you can rank a channel's most-watched moments.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.