List a Twitch channel's public past-broadcast videos

View all Twitch Channel, Clips, Videos & Stream Data endpoints →

Returns the public video (past broadcast) collection that is currently available for one Twitch channel, looked up by channel login. Send the required channel parameter (for example ninja) and, on later pages only, the optional numeric cursor returned for the same channel. The response is wrapped as {status, request_id, message, data}, and the records sit under data.user. Observed in a live probe for channel ninja: data.user.id (channel id), data.user.videos (12 edges per page), and data.user.cursor (an integer, 2 on the first page) as the page-level continuation value. Each edge carries an opaque cursor string and a node with id, title, publishedAt (ISO 8601 UTC), lengthSeconds, viewCount, previewThumbnailURL, animatedPreviewURL, game (id, name, displayName, slug, boxArtURL), owner (id, login, displayName, profileImageURL, primaryColorHex, roles.isPartner), self.isRestricted, resourceRestriction and contentTags. In that probe the videos came back newest first, resourceRestriction was null and contentTags was an empty list; populated values for those two fields, the second page, and the end of the collection were not observed. Pagination: omit cursor on the first request, keep channel identical, reuse the returned continuation value unchanged, stop when it is missing or repeats, and deduplicate by video id. Scope: the response reflects available video records, not a complete historical archive; deleted, expired or restricted recordings may be absent. The operation returns metadata and image links only and does not download media.

API Features

Past-broadcast records by channel login One call with a channel login returns the public video collection for that Twitch channel, with no developer app registration or token handling on your side.
Core VOD metrics on every node Each video node carries id, title, publishedAt, lengthSeconds and viewCount, enough to measure upload cadence, recording length and audience size per broadcast.
Static and animated preview links previewThumbnailURL and animatedPreviewURL give ready image links for video galleries and dashboards; the operation links to images but never downloads or streams media.
Game attached to each recording The game object (id, name, displayName, slug, boxArtURL) shows what was being played or discussed in each broadcast, so videos can be grouped by category.
Owner block with partner flag Every node repeats the owner (id, login, displayName, profileImageURL, primaryColorHex and roles.isPartner), so a video record stays attributable without a second channel lookup.
Continuation value for the video list The response returns 12 videos per page plus a page-level data.user.cursor; pass it back unchanged with the same channel to continue the collection, and stop when it is missing or repeated.

Live API Demo

GET /api/project/twitch-scraper/list-channel-videos

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/twitch-scraper/list-channel-videos?key=<API_KEY>&channel=ninja'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the list channel videos endpoint return?

It returns the public past-broadcast videos currently available for a Twitch channel. In the live probe for channel ninja, data.user.videos held 12 edges, each with a cursor string and a node containing id, title, publishedAt, lengthSeconds, viewCount, preview image links, game, owner and restriction fields.

How do I get the next page of videos?

Leave cursor out on the first request. For later pages send the same channel plus the page-level data.user.cursor value from the previous response, unchanged. In the probe that value was an integer (2 on the first page), which matches the numeric cursor parameter. Stop when it is missing or repeats, and deduplicate by video id.

Can I pass the cursor string found on each video edge?

No. The per-edge cursor values seen in the probe are opaque pipe-separated strings, while the cursor parameter is numeric. Use the page-level data.user.cursor value instead.

Does it return every broadcast the channel has ever streamed?

No. The response reflects available video records, not a complete historical archive. Deleted, expired or restricted recordings may be absent, so treat the totals you collect as coverage of available videos only.

Does this endpoint download or stream the video files?

No. It returns metadata and image links such as previewThumbnailURL and animatedPreviewURL. It does not fetch, store or transcode the recordings themselves.

What is the difference between videos and clips for a channel?

Videos are the past-broadcast recordings of the channel, while clips are a separate collection served by the channel clips operation. Both are cursor-paginated per channel, so call each one on its own and join the results on your side if you need both.

What happens for an unknown channel or a channel with no videos?

That case was not covered by the probe, which only used channel ninja, so the exact response is unverified. Check the status and message fields and handle an empty or missing data.user.videos list defensively.

Is the data real time or a snapshot?

Each response is a point-in-time read of the public video collection, so counts such as viewCount can change between calls. For live status use the stream operations instead, which are separate endpoints.

Related operations

Guides

View Subscription Plans →