Rumble Scraper

At a glance: what it does is extract public Rumble video, channel, Shorts, livestream, and comment data; input examples include channel handles, search terms, video URLs, and Shorts URLs; output examples are video rows and optional comment rows; use cases include media monitoring and content research; limitations, troubleshooting, and pricing/cost notes are covered below.

Rumble Scraper extracts structured data from public Rumble videos, Shorts, channel pages, livestream tabs, and available comments for media monitoring, content research, creator tracking, competitor analysis, and archive workflows.

The Actor is optimized as a two-stage pipeline. Channel and search inputs run as low-cost discovery jobs that return video URLs. Direct Rumble video URLs run as stable detail jobs, with comments available as an opt-in enrichment.

Main Use Cases

• Monitor public Rumble videos from known channels
• Collect Rumble video metadata for research or analytics
• Track creators, competitors, publishers, and campaigns
• Export public comment counts and accessible comment rows
• Build archives of public Rumble video URLs, titles, thumbnails, and channel details
• Feed clean Rumble datasets into spreadsheets, dashboards, APIs, or automation tools

What Data You Get

Video rows can include:

• Video URL, ID, slug, title, format, thumbnail, embed URL, duration, and scraped time
• Description, publish text or timestamp, status, live/upcoming indicators, and engagement counts when available
• Channel name, URL, slug, follower count, and verification state when visible
• Source fields showing which query and listing page produced the row
• Comment count, comment-access status, and comment-fetch status

Comment rows can include:

• Comment text, URL, author name, author profile URL, posting time, reactions, reply count, parent comment, depth, and source video
• One dataset row per public comment when Rumble exposes comment text without sign-in

Input Configuration

Choose Domains for Rumble channel/domain discovery, or URLs for direct Rumble video and Shorts URLs.

Channel discovery finds video URLs without fetching comments:

{
  "inputType": "domains",
  "queries": ["@NewsmaxTV"],
  "maxItems": 25
}

Details enriches direct video URLs and can fetch comments when needed:

{
  "inputType": "urls",
  "queries": ["https://rumble.com/v2n8po6-newsmax-tv-live-real-news-for-real-people.html"],
  "maxItems": 1,
  "includeComments": false
}

• inputType: choose domains for channels/handles, or urls for direct video and Shorts URLs.
• queries: Rumble video URLs, Shorts URLs, channel URLs, @channel handles, channel:name, or search:keyword.
• maxItems: maximum number of video rows to save.
• includeComments: fetch public comment count and accessible comments when available. Ignored during discovery.

Cost controls such as discovery source limits, blocked-request limits, first-page discovery, comment caps, proxy defaults, and the discovery cache are managed automatically.

Example Output

{
  "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/example.jpg",
  "embedUrl": "https://rumble.com/embed/v2kna8i/",
  "durationSeconds": 65535,
  "commentsCount": 15300,
  "commentsAccessRequired": true,
  "commentsScrapedCount": 0,
  "channelName": "NEWSMAX",
  "channelUrl": "https://rumble.com/c/NewsmaxTV",
  "sourceType": "oembed",
  "scrapedAt": "2026-06-12T11:58:06.061Z"
}

Comment rows use type: "comment" and include fields such as commentText, commentAuthorName, commentPostedAt, commentScore, commentIsReply, videoUrl, and channelName.

How To Run On Apify

1. Open the Actor in Apify Console.
2. Choose Domains for channel discovery or URLs for direct video URLs.
3. Export the videoUrl column from the discovery dataset.
4. Run details with those direct video URLs. Enable comments only when you need comment rows.
5. Open the Dataset tab when the run finishes.

Exporting Results

After a run, open the default dataset and export results as JSON, CSV, Excel, XML, RSS, or HTML. Video and comment rows can be filtered by the type field.

Python API Example

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

discovery_run = client.actor("thescrapelab/Apify-Rumble-Scraper").call(
    run_input={
        "inputType": "domains",
        "queries": ["@NewsmaxTV"],
        "maxItems": 25,
    },
    memory_mbytes=512,
    timeout_secs=120,
)

video_urls = [
    item["videoUrl"]
    for item in client.dataset(discovery_run["defaultDatasetId"]).iterate_items()
    if item.get("type") == "video" and item.get("videoUrl")
]

details_run = client.actor("thescrapelab/Apify-Rumble-Scraper").call(
    run_input={
        "inputType": "urls",
        "queries": video_urls,
        "includeComments": False,
    },
    memory_mbytes=512,
    timeout_secs=120,
)

for item in client.dataset(details_run["defaultDatasetId"]).iterate_items():
    print(item["type"], item.get("title") or item.get("commentText"), item["videoUrl"])

Limits And Caveats

• This Actor collects public Rumble data only. It does not log in, bypass paywalls, or access private content.
• Some videos show public comment counts but require sign-in to view comment text. Those rows return commentsAccessRequired: true.
• Rumble can aggressively challenge or block channel/search listing pages. Direct video URL batches are the recommended low-cost workflow.
• Discovery runs are capped to one listing page per source and skip previously discovered video URLs by default.
• Direct-video detail runs do not use Apify residential proxy by default. Discovery uses residential proxy because channel/search listings are more likely to block datacenter traffic.
• Search inputs are less reliable than direct channel or video URLs.
• Non-Rumble URLs are rejected instead of being treated as search terms.

Troubleshooting

• No results from a channel: try a direct video URL from that channel first. If direct video works, the listing page is likely blocked or temporarily challenged.
• Blocked or challenged listings: the Actor stops after repeated blocked requests to avoid runaway residential proxy transfer. Use direct video or Short URLs where possible and retry later if Rumble is heavily challenging channel pages.
• Runs are expensive: use the two-stage flow and leave includeComments set to false unless you need comment rows.
• Comments are missing: Rumble may require sign-in for comment text. Check commentsAccessRequired.
• Invalid input: use only Rumble URLs, @channel handles, channel:name, or search:keyword.

Pricing Notes

Use Apify pay-per-event pricing with custom events. Direct-video detail batches are very cheap at the platform level because they avoid residential proxy by default. Channel/search discovery can cost more when Rumble challenges listing pages, so the Actor caps discovery batches, uses a discovery cache, stops after repeated blocked requests, and charges a small discovery-source event before each accepted discovery source is attempted.

Recommended event configuration:

Event name	Event title	Price
apify-actor-start	Actor start	$0.002
discovery-source-attempt	Discovery source attempted	$0.003
discovery-video-url	Discovery video URL	$0.002
detail-video-result	Detail video result	$0.006
comment-row	Comment row	$0.001

Do not rely only on apify-default-dataset-item for this Actor. Discovery can return zero rows when Rumble blocks listings, so the discovery-source-attempt event is needed to keep blocked discovery runs from losing money.

FAQ

Can this scrape Rumble comments?

Yes, when Rumble exposes public comment HTML without sign-in. If Rumble requires sign-in, the Actor records the public comment count and marks commentsAccessRequired.

Can this scrape Rumble channels?

Yes, but channel listing pages are more likely to be blocked than direct video metadata. Start with direct video URLs for reliability.

What is the cheapest way to scrape Rumble data?

Run discovery on small channel batches, then run details on the discovered direct video URLs. Leave comments disabled unless you need them, and keep the discovery cache enabled.

Does this use the official Rumble logo or private Rumble data?

No. The Actor uses its own branding and collects only public data available from Rumble pages and public metadata endpoints.

Why did my run save zero items?

The most common causes are blocked channel/search listing pages, unsupported URLs, or a channel page with no public listing cards. Try a direct video URL to confirm the Actor is working.