Rumble Scraper

Extract structured data from public Rumble channels, videos, Shorts, livestream tabs, and available comment metadata. This Rumble scraper is built for Apify users who need export-ready video metadata for media monitoring, content research, creator tracking, lead generation, competitor analysis, and archive workflows.

The Actor starts with a lightweight HTTP crawl for low cost. Direct video URLs use Rumble metadata directly. If a channel listing is blocked, the Actor automatically retries with a single-browser fallback using US Residential proxy settings.

What You Can Scrape

• Rumble channel URLs such as https://rumble.com/c/NewsmaxTV
• Channel handles such as @NewsmaxTV
• Explicit channel inputs such as channel:NewsmaxTV
• Rumble video URLs
• Rumble Shorts URLs
• Channel tabs for videos, shorts, and livestreams
• Public comment counts, public replies, comment reactions, and one dataset row per public comment when Rumble exposes comments without login
• Search terms using search:keyword, although direct channel and video URLs are more reliable

Input

Most runs use three core fields plus an optional comments toggle.

{
  "queries": ["@NewsmaxTV"],
  "contentTypes": ["videos"],
  "maxItems": 25,
  "includeComments": true
}

• queries: Rumble URLs, channel handles, or search: terms
• contentTypes: channel tabs to scrape, usually videos
• maxItems: maximum number of video records to save
• includeComments: scrape public Rumble comments, which are the closest Rumble equivalent to reviews

Advanced reliability settings are handled automatically behind the scenes: US Residential proxy, bounded concurrency, up to 5 listing pages per source, direct-video metadata fetching, and browser fallback for blocked listing pages.

Output

Dataset items use a type field so exports are easy to filter:

• type: "video" rows contain one scraped video.
• type: "comment" rows contain one public comment or review, with the parent video, channel, and source fields copied onto the row.

Common fields include:

• type, videoId, videoSlug, videoUrl, title, videoTitle, description, format
• thumbnailUrl, embedUrl, duration, durationSeconds
• publishedAt, publishedAtText, scheduledAtText
• viewsCount, commentsCount, likesCount, engagementCount
• commentsScrapedCount, commentsAccessRequired, commentsFetchFailed
• commentText, commentUrl, commentAuthorName, commentAuthorUsername, commentAuthorProfileUrl
• commentPostedAtText, commentPostedAtTitle, commentPostedAt
• commentLikesCount, commentUpvotesCount, commentDownvotesCount, commentScore
• commentRepliesCount, commentIsReply, commentParentId, commentParentAuthorName, commentDepth
• channelName, channelSlug, channelUrl, channelFollowersCount, channelIsVerified
• sourceType, sourceValue, sourcePageUrl, sourcePageNumber, sourcePosition
• detailFetchFailed, detailFetchError, scrapedAt

Reliability

Rumble uses Cloudflare and can block low-trust traffic. This Actor is tuned for Apify cloud runs:

• Direct video URLs are the cheapest and fastest path.
• Channel URLs and handles are the most reliable listing inputs.
• Blocked channel pages automatically retry with a browser fallback.
• Search pages can return empty or challenge responses even in a browser; use direct channels when possible.
• The default 512 MB memory and 600 second timeout are used so blocked channel runs have enough headroom for browser fallback and comment rows.

Cost Controls

The Actor is priced per result and is designed to stay profitable by keeping the expensive browser path narrow:

• Direct video URLs avoid the browser and use a lightweight metadata endpoint.
• Direct video URLs can include public comment, reply, profile, timestamp, and reaction data when Rumble exposes it without login.
• Comment text is capped at 25 public comments per video to keep runs predictable.
• Each public comment is saved as its own dataset row, so comment scraping can produce more rows than maxItems.
• Channel listings only launch a browser after HTTP scraping is blocked.
• Browser fallback runs with concurrency 1.
• Images, fonts, CSS, and media are blocked in browser fallback to reduce Residential proxy transfer.
• Video rows are capped by maxItems.

For the best cost-to-output ratio, scrape channel handles or direct channel URLs with contentTypes: ["videos"].

Example Python API Usage

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")

run = client.actor("thescrapelab/Apify-Rumble-Scraper").call(
    run_input={
        "queries": ["@NewsmaxTV"],
        "contentTypes": ["videos"],
        "maxItems": 25,
        "includeComments": True,
    }
)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    if item["type"] == "comment":
        print(item["commentText"], item["videoUrl"])
    else:
        print(item["title"], item["videoUrl"])

Use Cases

• Rumble video scraping for market research
• News and political media monitoring
• Creator and influencer tracking
• Competitor content analysis
• Brand and topic monitoring
• Metadata collection for analytics pipelines
• Exporting Rumble video data to CSV, APIs, or automation workflows

Limits

This Actor only collects publicly available Rumble data. It does not log in, access private content, bypass paywalls, or collect private user data.

Some Rumble videos show the comment count publicly but require sign-in to view the comment text. In those cases, the Actor returns commentsAccessRequired: true and does not attempt to log in.