List Twitch Channel Clips by Login
View all Twitch Channel, Clips, Videos & Stream Data endpoints →Returns the public Twitch clips for one channel as a cursor-paginated collection that is separate from the channel's videos and live-stream data. Inputs: channel (required) is the channel login shown in the public Twitch URL, for example ninja, not a display title; cursor (optional, number) is the continuation value returned by a previous response for the same channel and is omitted on the first request. Observed in a live probe for channel ninja: the response is the standard envelope {status, request_id, message, data} with status 'ok' and a null message, and data.user holds the channel id, a clips array of 12 entries and a top-level cursor (an integer in the probe). Each clips entry is {cursor, node}; the per-entry cursor was null for the first eleven entries and a string on the last one. Each node carried id, slug, url, embedURL, title, viewCount, language, thumbnailURL, createdAt, durationSeconds and isFeatured, plus nested curator (id, login, displayName), game (id, slug, name, boxArtURL), broadcast (id, startedAt, title) and broadcaster (id, login, displayName, profileImageURL, primaryColorHex, roles) objects; champBadge and guestStarParticipants were null. These field names come from a single probe and may not be present on every clip, and the next-page behavior of the cursor was not exercised in the probe. Clip availability changes over time: a result does not guarantee downloadable media or perpetual access, and the list should not be assumed to contain every historical clip.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/twitch-scraper/list-channel-clips API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/twitch-scraper/list-channel-clips?key=<API_KEY>&channel=ninja'
Query Result
Use Cases
- Build a weekly highlight digest by picking fresh clips of a tracked streamer for a newsletter or social queue
- Collect clip titles and creation timestamps around a sponsored campaign window as mention evidence
- Feed a moderation or community-manager review queue with newly created clips from a team channel
- Deduplicate clips by source clip id across cursor pages and stop paging when a continuation repeats
- Show the latest 12 clips per channel on a content-discovery page with links back to the source clip
Frequently asked questions
What do I pass as the channel parameter for the clips list?
Pass the channel login shown in the public Twitch URL, for example ninja. A display title or a free-text name is not a login; if you only know a name, use Search Channels first and take the login from the result.
How do I page through a channel's clips?
Omit cursor on the first request. The probe response included a top-level cursor on data.user (an integer) next to the clips array; pass the continuation value from the previous response back unchanged with the same channel, and stop when it is missing or repeats. The next-page request itself was not exercised in the probe.
How many clips does one request return?
The probe for channel ninja returned 12 clips in the clips array. Page size is not an input of this operation, so plan for roughly a dozen clips per page.
Are the per-clip cursor values safe to use for paging?
Do not rely on them. In the probe the cursor inside each clips entry was null for the first eleven entries and a string on the last one, while the top-level cursor on data.user was an integer matching the numeric cursor parameter.
Does the list include every clip the channel has ever had?
No. Treat it as the collection the source exposes at request time. Clips can be removed or become unavailable, a result does not guarantee downloadable media or perpetual access, and the list should not be assumed to be a complete history.
Which fields identify a clip and tell me who made it?
Use node.id, node.slug, node.url and node.embedURL to identify and link a clip, node.curator for the account that created it, node.broadcaster for the channel that was clipped, and node.game for the category being played.
Do I need a Twitch developer account or access token to call this?
No. The request needs only your API key for this service and the channel login; you do not register a Twitch application or refresh Twitch tokens yourself.