Twitch API

Scrape Twitch data with one API

Name: Twitch Data API
Brand: SocialCrawl
Availability: InStock

Fetch public Twitch data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/twitch

4 active endpoints

GET /v1/twitch/profile
GET /v1/twitch/user/videos
GET /v1/twitch/user/schedule
GET /v1/twitch/clip

What Twitch endpoints does SocialCrawl ship?

4 live read endpoints for public Twitch data. Profiles, videos, schedule, and clips. Data API only.

Profile

1 credit

/v1/twitch/profile

Get Twitch streamer profile.

handle

User videos

1 credit

/v1/twitch/user/videos

List a Twitch user's videos.

handle, filter_by, sort_by

Schedule

1 credit

/v1/twitch/user/schedule

Get a Twitch user's stream schedule.

handle

Clip

1 credit

/v1/twitch/clip

Get Twitch clip details.

url

Twitch API4 endpoints supported

View docs

Returns a Twitch streamer's public profile: display name, follower count, bio, profile image URL, broadcast language, and partner status.

Use it for a snapshot of a channel by handle, before pulling that channel's videos or its upcoming schedule.

1 credit

GET/v1/twitch/profile?handle=ninja

handle

handle · Twitch username

$ curl https://www.socialcrawl.dev/v1/twitch/profile?handle=ninja \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the Twitch API works

Twitch is a normal SocialCrawl social surface. You call GET /v1/twitch/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/twitch/profile

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/twitch/user/videos

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/twitch/user/schedule

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/twitch/clip

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/twitch/profile
  ?handle=ninja
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authorprofile

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postuser/videos

items[].post with id, url, content, engagement, author, published_at, ext

CommentListuser/schedule

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediaclip

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

Twitch is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What Twitch is for this API

Public Twitch surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

public profile / channel→ author.*profile identity and counters

public post / media→ post.* / items[].postpost content and engagement

list / search page→ items[] or hitscomments or search hits when present

What this API is used for

The jobs this API is most often used for.

4active Twitch endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

Streamer schedule and VOD monitoring

Callers concentrate on profile, content lists, search, and deepen paths on Twitch. Structured Twitch JSON on the shared schema with one SocialCrawl API key.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

What people build with the Twitch API

The jobs Twitch data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

Creator analyticsStreamer profile, past broadcasts and the upcoming schedule.

Influencer discoveryStreamer profile, past broadcasts and the upcoming schedule.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on Twitch. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on Twitch.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/twitch/profile?handle=ninja" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/twitch/user/videos?handle=ishowspeed" \
  -H "x-api-key: sc_your_api_key_here"

Twitch on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Twitch API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProfileGet Twitch streamer profile ClipGet Twitch clip details User VideosList a Twitch user's videos User ScheduleGet a Twitch user's stream schedule

Comparison

How does SocialCrawl compare to Twitch Helix API for Twitch data?

Same Twitch data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	Twitch Helix API
Authentication	One x-api-key header	App access token via OAuth client-credentials flow
Setup	Sign up and call in minutes	Developer console app registration with client ID and secret
Rate limits	Credit-based: your only quota is your balance	Token-bucket rate limits tracked per client
Response schema	Unified JSON shared across 51 platforms	Helix-specific response objects
Pricing	1 credit per request; 100 free credits on signup	Free within rate limits for registered apps
Data coverage	Profiles, clips, channel videos, and broadcast schedules	Broad official coverage, including streams and chat with scopes
Maintenance	One key covers Twitch plus 50 other platforms	Token refresh and Helix version changes are on you

Authentication

SocialCrawl

One x-api-key header

Twitch Helix API

App access token via OAuth client-credentials flow

Setup

SocialCrawl

Twitch Helix API

Developer console app registration with client ID and secret

Rate limits

SocialCrawl

Credit-based: your only quota is your balance

Twitch Helix API

Token-bucket rate limits tracked per client

Response schema

SocialCrawl

Unified JSON shared across 51 platforms

Twitch Helix API

Helix-specific response objects

Pricing

SocialCrawl

1 credit per request; 100 free credits on signup

Twitch Helix API

Free within rate limits for registered apps

Data coverage

SocialCrawl

Profiles, clips, channel videos, and broadcast schedules

Twitch Helix API

Broad official coverage, including streams and chat with scopes

Maintenance

SocialCrawl

One key covers Twitch plus 50 other platforms

Twitch Helix API

Token refresh and Helix version changes are on you

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

How do I build a Twitch scraper?

A Twitch scraper reads channels, clips and streams as JSON. SocialCrawl returns them from 4 Twitch endpoints on the same key and the same unified schema as YouTube and Kick, so you can compare a creator across every streaming platform without writing three parsers.

How do I scrape Twitch data with an API?

SocialCrawl provides 4 Twitch API endpoints covering streamer profiles, clip details, and a channel's video history. Send a GET request with x-api-key. No Twitch developer app, no OAuth, no Helix client-credentials flow required.

What Twitch endpoints does SocialCrawl offer?

4 endpoints: Profile, Clip, User Videos, and User Schedule. Same unified schema as every other SocialCrawl platform.

Is this a Twitch Helix API alternative?

Yes. Unlike Twitch's Helix API, SocialCrawl does not require a registered developer app, OAuth client credentials, or access-token refresh. One x-api-key reads public streamer and clip data, and the schema matches the other 50 platforms we support.

How much does the Twitch API cost?

All 4 Twitch endpoints cost 1 credit per request on the standard tier. New accounts get 100 free credits with no credit card required, enough to make 100 Twitch calls before you pay a cent and test all 4 endpoints end-to-end.

Is scraping Twitch clips and profiles legal?

SocialCrawl reads only publicly visible Twitch data through our upstream provider. You are responsible for complying with Twitch's Developer Services Agreement, terms of service, and any data protection regulations that apply to your specific use case. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.

Can I use the Twitch API for creator discovery and ad research?

Yes. The profile endpoint returns follower counts, partner/affiliate status, and broadcast language, ideal for influencer shortlisting. The clip endpoint returns view counts and game tags, useful for finding high-engagement viral moments to repurpose.

What is the best Twitch scraper API?

SocialCrawl is the fastest way to read public Twitch data without a Helix app: 4 endpoints (profile, clip, channel videos, broadcast schedule) at 1 credit per request, with 100 free credits and no card. The official Helix API is free and broader, but requires app registration, OAuth tokens, and per-client rate-limit handling.

Is there a Twitch data API?

Yes. SocialCrawl is a Twitch data API for public reads, covering streamer profiles, clip details, channel video history, and broadcast schedules in one unified schema. Twitch's official Helix API is free and broader, but it requires a registered app, OAuth client credentials, and per-client rate-limit handling. SocialCrawl skips all three, at 1 credit per request with 100 free credits on signup.

Twitch scraping API vs the official Twitch API: what's the difference?

With SocialCrawl there is no app review or approval queue. Sign up and call Twitch endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Related APIs and tools

Adjacent endpoints and free tools on SocialCrawl. The tools run without an API key.

youtube scraper api

Read the Twitch API reference in the docs

🤖 AI agent or LLM? Read this page as markdown