Twitch data API
Read streamers, videos, clips and schedules from Twitch with one key and one response shape.
Twitch streamer profiles, a channel's videos and highlights, individual clip details, and the schedule a streamer has published.
user/videos returns one fixed set of up to 100 rows and that is the whole
result. There is no cursor and nothing to page, so use filter_by and
sort_by to make those 100 the right 100 rather than expecting to walk a full
history.
Your first call
1. Fetch a profile
curl "https://www.socialcrawl.dev/v1/twitch/profile?handle=ninja" \
-H "x-api-key: sc_your_key_here"const res = await fetch(
"https://www.socialcrawl.dev/v1/twitch/profile?handle=ninja",
{ headers: { "x-api-key": process.env.SOCIALCRAWL_API_KEY! } },
);
const { data } = await res.json();
console.log(data.author.display_name, data.author.followers);import os
import requests
res = requests.get(
"https://www.socialcrawl.dev/v1/twitch/profile",
params={"handle": "ninja"},
headers={"x-api-key": os.environ["SOCIALCRAWL_API_KEY"]},
)
data = res.json()["data"]
print(data["author"]["display_name"], data["author"]["followers"])Measured on 22/11/2026: this call returned the Ninja channel with its follower count and bio for 1 credit. A Twitch profile has no following or post count, so those fields come back null.
2. Fetch their content
curl "https://www.socialcrawl.dev/v1/twitch/user/videos?handle=ninja&sort_by=VIEWS" \
-H "x-api-key: sc_your_key_here"3. Read computed fields
When an endpoint supports a computed field and the required source inputs are present, the unified response includes that optional field. Depending on the endpoint, optional fields can include engagement_rate, language, content_category, and estimated_reach. See Computed fields for formulas, clamping rules, and null semantics. Where an endpoint supports them, list rows also carry judged labels (computed.labels, computed.relevance) by default at no extra credits; see Labels.
What it covers
| What you want | Call |
|---|---|
| A streamer's followers count and bio | GET /v1/twitch/profile |
| Past videos and highlights | GET /v1/twitch/user/videos |
| The most viewed videos | GET /v1/twitch/user/videos with sort_by=VIEWS |
| When a streamer plans to go live | GET /v1/twitch/user/schedule |
| One clip with its view count | GET /v1/twitch/clip |
What it does not cover
- Live viewer counts and who is streaming right now are not returned.
- Chat logs and subscriber lists are not returned.
- Archived past broadcasts.
filter_by=ARCHIVEis rejected before billing, soHIGHLIGHTandUPLOADare the kinds that exist. - Nothing on this platform paginates, so there is no deep paging.
- Keyword search for channels or clips. Start from a handle or a clip URL you already have.
Channels
filter_by picks the kind, HIGHLIGHT or UPLOAD, and sort_by is TIME for newest first or VIEWS. Both enums are uppercase. The schedule endpoint returns each segment's start and end time, title, categories and cancellation flags.
curl "https://www.socialcrawl.dev/v1/twitch/user/schedule?handle=kaicenat" \
-H "x-api-key: sc_your_key_here"Clips
user/videos covers past broadcasts, clip covers one shared moment, and user/schedule covers what has not happened yet. A clip returns its title, view count, duration, creator and broadcaster names, game, thumbnail and creation time.
curl "https://www.socialcrawl.dev/v1/twitch/clip?url=https://www.twitch.tv/ninja/clip/BeautifulSolidYamOSkomodo-NXBFNORy-qFIXZ9R" \
-H "x-api-key: sc_your_key_here"All endpoints
4 endpoints available.
| Endpoint | Path | Credit Tier |
|---|---|---|
| Get Twitch clip details | /v1/twitch/clip | standard (1cr) |
| Get Twitch streamer profile | /v1/twitch/profile | standard (1cr) |
| Get a Twitch user's stream schedule | /v1/twitch/user/schedule | standard (1cr) |
| List a Twitch user's videos | /v1/twitch/user/videos | standard (1cr) |
How far back and how deep
Each list returns one page at a time. Send cursor for the next page, or max_items or max_pages to collect several pages in one call. A page size appears only where it has been verified. How paging works
| Path | Rows per page | Date window | One call collects |
|---|---|---|---|
/v1/twitch/user/videos | varies | since and until, applied to each page fetched | one page a call |
Platform notes
channel.schedule is null when the streamer has not published one. Plenty of channels never fill it in, so treat a null schedule as normal rather than as an error. The call succeeds and returns nothing; do not branch on it failing.
Identifiers split two ways. profile, user/videos, and user/schedule take a handle without the @; clip takes the clip url.
