All platforms

Rumble scraper API

Search public Rumble results, page channel uploads, resolve video metadata, pull comments, and read captions over REST. Same JSON envelope as YouTube and the rest of the catalog.

5 endpoints

Why teams use Social Fetch for Rumble

Newsrooms, brand monitors, and agency research desks that already crawl YouTube still miss creators who publish first (or only) on Rumble. The coverage gap shows up in political and alternative-media briefs, live-stream watchlists, and keyword jobs that assume every clip lives on Google's index. Homegrown Rumble scrapers rarely get the same care as YouTube jobs — until a client asks for that platform by name.

What those pipelines actually need is five boring jobs: free-text search that returns videos, Shorts, channels, playlists, and live streams in one response; a channel upload list for a known `/c/` or `/user/` URL; single-video detail (title, metrics, caption track listings); top-level comments for research samples; and spoken captions when a track exists. Selector churn and player markup changes make each of those painful to maintain in-house.

Social Fetch exposes them as ordinary GET routes under `/v1/rumble/...`. You pass a query or public URL and get structured JSON with `data.lookupStatus` where the operation defines it, plus `meta.requestId` and `meta.creditsCharged`. Failed upstream lookups surface as typed outcomes — not an empty 200 that looks like a deleted video.

The same API key covers the rest of the marketplace catalog (17 platforms, 137 endpoints), so a YouTube + Rumble monitoring fan-out does not need a second vendor or a second auth scheme. Publishing, ads, and partner integrations stay with Rumble's own products when those exist for your use case.

What Rumble data can you get?

  • Keyword search across videos, Shorts, channels, playlists, and live streams.
  • Channel upload lists (videos + Shorts) by public channel or user URL.
  • Single video detail — title, description, metrics, channel, captionTracks.
  • Top-level comment threads for research and moderation samples.
  • Video transcripts (plainText and timed segments) when captions exist.
  • Shared `{ data, meta }` envelope with YouTube, TikTok, and the rest of the catalog.
  • Public data only — private or deleted content resolves as typed not-found outcomes.

Rumble API endpoints

Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.

How to call the Rumble API

  1. 1. Create a key and smoke-test search

    Sign up at Social Fetch and copy an `sfk_…` key. New accounts get 100 free credits. Start with `GET /v1/rumble/search?query=…` against a real monitoring phrase so you see the five result buckets, cursors, and `meta.creditsCharged` before you wire batch jobs.

  2. 2. Follow search → channel → video

    From a channel hit, page uploads with `GET /v1/rumble/channels/videos`. Hydrate a watch URL with `GET /v1/rumble/videos`, then optionally `.../comments` or `.../transcript`. Pass `x-api-key` on every call; continue with `cursor` when `data.page.hasMore` is true.

  3. 3. Join rows to your monitoring schema

    Branch on `data.lookupStatus` before upserting (where the route exposes it). Store video ids, channel urls, view counts, and caption text beside your YouTube rows. Log `meta.requestId` on bad rows so support can trace the exact call.

How much does the Rumble API cost?

Rumble routes are credit-metered per completed lookup. Search, channel videos, video detail, and comments document flat costs on each operation page — always trust `meta.creditsCharged`. Transcripts bill when captions are found and do not charge when captions are unavailable (see the transcript operation note). Credits never expire on pay-as-you-go packs. Signup includes 100 free credits.

See credit packs

Social Fetch vs the official Rumble API

Rumble does not offer a simple public REST catalog for arbitrary keyword search, channel uploads, comments, and captions on watch URLs you did not authorize. Partner or publisher APIs (when available for your account) are the right stack for first-party publishing and authenticated product features. Social Fetch is public enrichment: query or URL in, normalized JSON out, no Rumble OAuth — built for multi-platform monitoring stacks that already use one Social Fetch key next to YouTube.

Rumble API FAQ

Is there a Rumble scraper API that works without a Rumble developer key?

Yes. Social Fetch Rumble routes read public search, channel, video, comment, and caption data. You authenticate to Social Fetch with an API key (`x-api-key`). You do not register a Rumble application or OAuth as the channel whose public data you are fetching.

What Rumble data does Social Fetch cover?

Five marketplace operations: keyword search (`GET /v1/rumble/search`), channel upload lists (`GET /v1/rumble/channels/videos`), single video by watch URL (`GET /v1/rumble/videos`), top-level comments (`GET /v1/rumble/videos/comments`), and transcripts (`GET /v1/rumble/videos/transcript`). Exact paths, parameters, and examples live under `/docs/api` and on this hub's endpoint list.

How do I search Rumble by keyword via API?

Call `GET /v1/rumble/search` with a required `query` string. The response splits into `data.videos`, `data.shorts`, `data.channels`, `data.playlists`, and `data.liveStreams`, plus `data.totalResults` for the current page. Pass `cursor` when `data.page.hasMore` is true. This route has no datePosted, sortBy, type, or duration filters — filter client-side if you need a time window.

How do I list videos for a Rumble channel?

Pass a public channel URL (`https://rumble.com/c/...` or `https://rumble.com/user/...`, or a bare handle the API accepts) to `GET /v1/rumble/channels/videos`. On a found lookup, read `data.channel`, `data.videos`, `data.shorts`, and `data.page`. Branch on `data.lookupStatus` before writing rows — `found` can still return empty arrays.

How do I get Rumble video metadata by URL?

Call `GET /v1/rumble/videos` with a public watch URL. On `found`, `data.video` can include title, description, thumbnail, duration, publish time, metrics (views, likes, dislikes), nested channel, embed/share URLs, live flags, and `captionTracks` when subtitle files are listed.

Can I pull Rumble video comments via API?

Yes. `GET /v1/rumble/videos/comments` returns top-level comments for a public video URL — author, text, likes, dislikes, and reply counts when Rumble exposes them. There is no separate comment-replies operation in the public Rumble catalog.

Can I get Rumble video transcripts?

Yes. Pass a public video URL to `GET /v1/rumble/videos/transcript`. On a found lookup, `data.transcript` includes `plainText` and optional timed `segments`. This route reads existing captions; it does not run speech-to-text when no track exists. Billing is documented on the operation page (charge when found; no charge when captions are unavailable) — confirm with `meta.creditsCharged`.

Rumble official API vs Social Fetch — which should I use?

Use Rumble's own partner or publisher products when you need write access, authenticated publishing, or first-party integrations they offer for your account. Use Social Fetch when you need public search, channel uploads, video detail, comments, and captions without a Rumble developer app — especially when those rows must sit next to YouTube in one warehouse schema.

How much does the Rumble API cost on Social Fetch?

You buy credit packs (or spend the 100 free signup credits). Per-route costs are listed on each operation page and in the API reference; always check `meta.creditsCharged` after each call. There is no required monthly subscription for pay-as-you-go packs.

Is scraping Rumble data legal?

Social Fetch returns publicly visible data. You are responsible for how you use it under Rumble's terms, applicable law, and your own compliance review. We do not give legal advice.

Start with Rumble search and video data

Create an account, spend the 100 free credits on a live keyword search and a watch-URL lookup, then buy a pack when the JSON fits your monitoring or research pipeline. Credits do not expire on pay-as-you-go packs.