Rumble Channel Videos API
Page a channel's public uploads and Shorts as structured rows — titles, durations, view counts, and watch URLs in the shared Social Fetch envelope.
GET /v1/rumble/channels/videos1 credit per successful request.
About this endpoint
Political and news monitors often already know the Rumble channel URL from a prior brief. What they need next is the recent upload list: titles, publish times, view counts, and a watch URL to fan out into video detail, comments, or transcript routes. Scraping the channel page yourself means chasing Rumble's markup and inventing your own page tokens every time the layout changes.
`GET /v1/rumble/channels/videos` takes a required `url` query param (a public Rumble channel link such as `https://rumble.com/c/...` or `https://rumble.com/user/...`, or a bare handle the API accepts). Optional `cursor` continues a previous page. On a found lookup you get `data.channel` (name, handle, url when available), `data.videos`, `data.shorts`, and `data.page` (`hasMore`, `nextCursor`). Each media row can include id, kind, url, title, thumbnailUrl, viewCount, publishedAt, durationSeconds, and related labels. Branch on `data.lookupStatus` before you write rows — HTTP 200 alone does not mean the channel resolved, and `found` can still return empty `videos` or `shorts` arrays.
Pricing is on the credit badge for this operation; bill from `meta.creditsCharged`. This route lists channel uploads. Single-video detail is `GET /v1/rumble/videos`. Spoken text is `GET /v1/rumble/videos/transcript`. Keyword discovery is `GET /v1/rumble/search`. Same API key across the Rumble tag.
Rumble Channel Videos API FAQ
How do I list Rumble videos for a channel via API?
Call GET /v1/rumble/channels/videos with your Social Fetch API key (x-api-key) and a public channel url query param. Read data.lookupStatus, then data.channel, data.videos, data.shorts, and data.page. Full parameters and examples are in the API docs.
How much does the Rumble channel videos API cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.
What URL formats does the channel videos endpoint accept?
Public Rumble channel URLs under /c/ or /user/, plus bare handles or @handles the API accepts for this route. Pass one url per request. Video watch URLs belong on GET /v1/rumble/videos, not here.
What does each channel video or Shorts row include?
id, kind (video, short, or live), url, title, thumbnailUrl, optional nested channel, viewCount, viewCountText, publishedAt, publishedTimeText, durationSeconds, durationText, and badges when present. Videos and Shorts are separate arrays on the same response.
How does pagination work on Rumble channel videos?
When data.page.hasMore is true, pass data.page.nextCursor as the cursor query param on the next request. Keep the same channel url across pages.
Does found always mean the channel has videos on this page?
No. lookupStatus found means the channel resolved. data.videos and data.shorts may still be empty when there are no items in the returned page. not_found means the channel URL did not resolve. Persist meta.requestId when you need to debug a miss.
How is this different from search or single-video detail?
This route pages uploads for a known channel URL. GET /v1/rumble/search is keyword discovery across Rumble. GET /v1/rumble/videos fetches one video by watch URL. Use the channel list to discover ids, then video, comments, or transcript routes for depth on a single clip.
Do I need a Rumble developer key to list channel videos?
No. You authenticate to Social Fetch with an API key. The route reads public channel upload data; it does not act on behalf of a logged-in Rumble user.