Real-time Twitch data, one API call.
Public Twitch channels, VODs, schedules, and clips as JSON — no Helix Client-ID or app access token.
The Twitch API from Captapi gives developers reliable access to public Twitch data without building or maintaining scrapers — send one authenticated request and get clean, structured JSON back. Channels, VODs, schedules, and clips without a Helix Client-ID.
curl "https://api.captapi.com/v1/twitch/profile?url=https%3A%2F%2Fwww.twitch.tv%2Fshroud" \
-H "Authorization: Bearer capt_live_..."What is the Twitch API?
Public Twitch channels, VODs, schedules, and clips as JSON — no Helix Client-ID or app access token. Every endpoint is a single authenticated GET request that responds with predictable JSON, so the data drops straight into dashboards, AI pipelines, RAG systems, and no-code automations. AI agents can call the same endpoints as MCP tools via @captapi/mcp.
Compared with Twitch Helix API: Use Captapi instead of Helix when you need public Twitch channel, VOD, schedule, or clip data and you do not want to register a Twitch application. Keep Helix when you must subscribe to EventSub, manage a channel you own, or call a write scope. Twitch Helix API alternative.
Endpoints
What you can do with the Twitch API
Profile
GET /v1/twitch/profile
Twitch channel — handle + displayName, socials[], topClips, schedule preview, stream only when live (1 credit).
1 credit
User Videos
GET /v1/twitch/user-videos
Twitch channel VODs — lean rows, video-id cursor, filter/sort, top-level broadcaster{} (flat 2).
2 credits
User Schedule
GET /v1/twitch/user-schedule
Twitch channel schedule — startAt/endAt, title, game, isRecurring (0 credits when empty).
1 credit
Clip
GET /v1/twitch/clip
Twitch clip — curator vs channel, signedVideoUrl, unwrapped token, relatedClips (1 credit).
1 credit
How it works
- 1. Sign up — get 100 free credits, no card required.
- 2. Create a key from your dashboard.
- 3. Call any endpoint above with
Authorization: Bearer capt_live_...and parse the JSON response. Passcache=trueto reuse a prior response from the 24h cache at no cost.
Twitch API guides
Frequently asked questions
What is the Twitch API?+
The Twitch API is a REST API from Captapi that returns public Twitch data as clean, structured JSON. It covers 4 endpoints — Profile, User Videos, User Schedule, Clip — behind one Bearer API key, with no OAuth flow and no infrastructure to build or maintain.
What data can I get from the Twitch API?+
Public Twitch channels, VODs, schedules, and clips as JSON — no Helix Client-ID or app access token. Each endpoint is a single GET request that responds with predictable JSON fields, so the data is ready for dashboards, AI pipelines, and automations.
Do I need a Twitch developer account or OAuth?+
No. You only need a Captapi key (capt_live_...), sent as an Authorization: Bearer header. The same key works across all 33 platforms Captapi supports. We handle access, rate limits, retries, and parsing for you.
How much does the Twitch API cost?+
Twitch endpoints cost between 1 and 2 credits per call, depending on the endpoint and how many results you request. New accounts start with 100 free credits (no credit card). Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d.
Can AI agents use the Twitch API?+
Yes. Every Twitch endpoint is exposed as a tool in the official MCP server (@captapi/mcp) for Claude, Cursor, and VS Code, and is also available through the @captapi/cli CLI and the n8n-nodes-captapi community node.
Is the Twitch API suitable for production use?+
Yes. It is a stable REST API with predictable JSON, automatic retries, and upstream fallbacks. Pass cache=true to serve from the 24h cache (0 credits on hit); default is always fresh. Selected profile endpoints also accept cacheMaxAge=1d|3d|7d|14d|30d. Only successful responses consume credits — failed or empty results are never charged.
Do I need a Twitch Client-ID or OAuth token?+
Not for Captapi. Helix does. Send Authorization: Bearer capt_live_… to /v1/twitch/profile, /user-videos, /user-schedule, or /clip. Clip MP4s are signed — signedVideoUrl includes expiresAt; persist the clip slug and refetch. Channel URLs on /clip are 400 (use /profile). VOD history stops at 100 — anonymous GQL rejects deeper cursors.
Explore other platforms
Start using the Twitch API in sixty seconds
Sign up, grab your API key, and make your first request. 100 credits on the house — no credit card.