Rumble Scraper | Channels, Videos & Shorts

Rumble Scraper: Channels, Videos & Shorts

Export public Rumble video metadata from video pages, channel tabs and search results in one run. Paste video URLs, channel URLs, @handles or search:keywords; the Actor recognises the input and runs the workflow for you.

Comment collection is currently unavailable. Public comment counts may still appear when the page exposes them. The Actor uses public HTML, without logging in or using Rumble source APIs, oEmbed or transcript services.

Quick start and input example

1. Paste one or more Rumble URLs or channel handles into What to scrape.
2. Keep Export snapshot selected.
3. Set Maximum videos and a spending limit, then start. Open Run summary to inspect delivery and coverage.

Most users can leave Advanced unchanged. A channel export returns visible listing metadata with fewer requests; direct video URLs return metadata available on those video pages.

{
  "workflow": "export",
  "queries": ["https://rumble.com/c/NewsmaxTV"],
  "maxItems": 5
}

You can mix direct video URLs, channel URLs and handles in the same run. Each video appears at most once. Only public Rumble video pages, channel/user tabs and video search inputs are supported; unrelated URLs are rejected.

Advanced settings and compatibility

Setting	Behaviour
detailLevel: "listing"	Default. Channel pages return visible listing metadata. Direct video inputs still fetch their video pages.
detailLevel: "full"	Fetch discovered video pages within the same run. More requests and costs; detail requests are capped by Maximum videos.
maxListingPages	New workflows: default 2, maximum 5 per source.
contentTypes	Advanced JSON input: videos, shorts, livestreams. Default videos; alternatively paste the specific tab URL.
includeComments	Hidden from the form; retained for API compatibility. Collection is unavailable and requested rows report that explicitly.
proxyConfiguration	Optional JSON override. Cloud requests use Residential US proxy by default. Explicit opt-out and custom proxy URLs are respected.
inputType, pipelineStage, useDiscoveryCache, discoveryCacheName	Legacy controls; cache settings are available only through JSON/API input. API inputs omitting workflow keep their previous stage/cache behaviour. Export snapshot detects sources automatically and does not use monitoring history.

Both SDK groups/countryCode and Console apifyProxyGroups/apifyProxyCountry proxy names are supported. Local direct-video inputs remain proxy-free by default.

For existing discovery integrations, inputType: "domains" still returns discovery rows with the existing named cache; useDiscoveryCache: false still requests a fresh legacy discovery snapshot. Existing direct-video detail inputs remain supported. New workflows do not require a second Actor call for enrichment.

Output and coverage

Video rows retain their existing fields, including:

• type, videoId, videoSlug, videoUrl, title, thumbnail and publication fields when observed.
• Visible views, comment counts, duration, live/upcoming status and channel information.
• sourcePageUrl, source type/value, position and extraction stage for traceability.
• Full mode adds available page descriptions and structured metadata; missing data is left unavailable.

Example from a direct-video snapshot (optional fields omitted):

{
  "type": "video",
  "pipelineStage": "details",
  "videoSlug": "v2n8po6",
  "videoUrl": "https://rumble.com/v2n8po6-newsmax-tv-live-real-news-for-real-people.html",
  "title": "NEWSMAX2 LIVE on Rumble",
  "thumbnailUrl": "https://hugh.cdn.rumble.cloud/video/s8/1/2/l/p/I/2lpIj.qR4e-small-NEWSMAX-TV-LIVE-Real-News-F.jpg",
  "scrapedAt": "2026-10-28T15:57:38.709Z"
}

The default dataset can be exported as JSON, CSV, Excel or other Apify formats. Run summary includes confirmed delivered counts, pages checked, source coverage, downloaded HTML bytes, process memory, billing counters and stop reasons.

Outcome	Meaning
items_found	Confirmed video rows were delivered.
no_matches	Supported pages confirmed no matching output.
partial	A result/page/detail/spending limit, invalid source or source failure prevented complete coverage.
failed	Sources were unavailable, delivery could not be confirmed, or history could not be safely saved.

A five-item limit can return one item when you supply one video URL. Legacy cached discovery can legitimately return zero rows. An empty response is not automatically proof that no videos exist: inspect source coverage and errors.

If a detail page fails, observed listing metadata may be retained with detailFetchFailed: true; the summary reports partial coverage. Unrecognised layouts, block pages and invalid video metadata are not delivered as successful empty results. Failed sources do not erase prior history. An uncertain delivery does not advance history, so retrying may return a previously delivered row whose delivery could not be confirmed.

Pricing and cost controls

Export pricing is unchanged: Free/Bronze $1.49 per 1,000 returned results, Silver $1.39, Gold and above $1.29. The startup event is $0.0005 per GB-start, with a minimum of one event. See the Pricing tab for the active rates and included platform usage.

Export snapshot does not charge monitoring-check fees. The approved monitoring price is scheduled to take effect on 11 November 2026 at 16:27 UTC. Monitoring is staged for release after pricing is active and billing verification passes; it is not available in the current input form.

Use small batches, keep listing metadata as the default, and set a spending cap. The Actor respects confirmed delivery limits and stops when a configured check/result charge cannot fit the budget. Counters describe confirmed deliveries and charges; network attempts are not result rows.

Python API example

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["APIFY_TOKEN"])
run = client.actor("thescrapelab/Apify-Rumble-Scraper").call(
    run_input={
        "workflow": "export",
        "queries": ["@NewsmaxTV"],
        "maxItems": 5,
    },
    max_total_charge_usd=0.05,
)
if run is None:
    raise RuntimeError("The Actor run did not finish")
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["title"], item["videoUrl"])

Use workflow: "export" for a fresh snapshot on every run. Monitoring will be enabled in a later verified release after its scheduled pricing activates. No manual discovery-to-details handoff is needed. Rumble can block public pages or change layouts; coverage is not guaranteed for every channel, tab or query.