Rumble API

Scrape Rumble data with one API

Name: Rumble Data API
Brand: SocialCrawl
Availability: InStock

Fetch public Rumble data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.

Read the docs How it works Try live

/v1/rumble

5 active endpoints

GET /v1/rumble/channel/videos
GET /v1/rumble/video
GET /v1/rumble/video/comments
GET /v1/rumble/video/transcript
GET /v1/rumble/search

What Rumble endpoints does SocialCrawl ship?

5 live read endpoints for public Rumble data. Channel videos, video detail, comments, transcripts, and search. Data API only.

Channel videos

1 credit

/v1/rumble/channel/videos

List videos for a Rumble channel.

handle, url, cursor

Video

1 credit

/v1/rumble/video

Get a Rumble video.

url

Video comments

1 credit

/v1/rumble/video/comments

List top-level comments on a Rumble video.

url

Video transcript

10 credits

/v1/rumble/video/transcript

Get a Rumble video transcript.

url

Search

1 credit

/v1/rumble/search

Search Rumble videos.

query, cursor

Rumble API5 endpoints supported

View docs

Returns Rumble videos and shorts matching a keyword, each with title, URL, thumbnail, channel, publish date, and view count.

Use it to find videos across all of Rumble, passing the returned cursor for the next page; channel/videos covers one named channel.

1 credit

GET/v1/rumble/search?query=funny+cats

query

query · Search query.

$ curl https://www.socialcrawl.dev/v1/rumble/search?query=funny+cats \
    -H "x-api-key: sc_YOUR_API_KEY"

idle

// Running this live needs your own API key. Hit "Try it" to see an example response

How the Rumble API works

Rumble is a normal SocialCrawl social surface. You call GET /v1/rumble/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.

Authenticate every call

Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.

GET with query params

Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.

Pay in credits, not seats

Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.

The usual integration chain

Most products resolve an account, page content, then deepen only the posts that matter.

01Account

GET /v1/rumble/channel/videos

Author-shaped profile

Resolve the handle or id once.

02Feed

GET /v1/rumble/video

PostList of recent public items

Page with cursor or after when the route supports it.

03Item

GET /v1/rumble/video/comments

Full Post for one URL or id

List rows are not enough when you need the full record.

04Comments

GET /v1/rumble/video/transcript

CommentList when the platform exposes it

Expand only when a thread matters.

request

GET /v1/rumble/channel/videos
  ?handle=example
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

response envelope

{
  "success": true,
  "data": { "/* Author | Post | PostList | CommentList | … */": true },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align.

Authorchannel/videos

id, username, display_name, avatar_url, bio, followers, url, ext

PostList / Postvideo

items[].post with id, url, content, engagement, author, published_at, ext

CommentListvideo/comments

items[] with author, content.text, engagement, published_at when comments ship

Search / Mediavideo/transcript

search hits, media metadata, or transcripts depending on route

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.

Validate, then debit

Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.

Normalize and return

Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.

Billing rules that matter in production

Standard live miss: tier cost (often 1 credit)
Advanced reads: typically 5 credits
Premium reads: typically 10 credits
Metered routes: min floor when documented
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
Disabled routes: 503, never charged

How we get the data

Rumble is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.

What Rumble is for this API

Public Rumble surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.

How SocialCrawl reaches it

Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.

What leaves our edge

Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.

What we do not ship live

No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.

field map sketch

upstream identity→ author.* / data rootprofile identity and counters

public post / media→ post.* / items[].postpost content and engagement

comment page / tree→ CommentList items[]comments or search hits when present

What this API is used for

The jobs this API is most often used for.

5active Rumble endpoints in the registry

1 / 5 / 10credit ladder across standard, advanced, premium

Rumble monitoring and content intelligence

Callers concentrate on profile, content lists, search, and deepen paths on Rumble. Structured Rumble JSON on the shared schema with one SocialCrawl API key.

Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.

What people build with the Rumble API

The jobs Rumble data is most often used for. Each one is a full recipe with the endpoint chain and pricing.

Video transcriptsSearch, video detail, comments and transcripts on the shared schema. Small surface, clean responses.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Monitoring jobs

Python, cron, Slack bots

Poll profiles and feeds on Rumble. Alert when engagement velocity jumps.

Research and VoC

Node, notebooks, BI loads

Search and expand posts for brand, product, and competitor language on Rumble.

Backend product jobs

Go, workers, Explorer

Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.

Call it in two lines

Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.

curl "https://www.socialcrawl.dev/v1/rumble/channel/videos?handle=example" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/rumble/video?url=https://rumble.com/v79xhhm-discovery-example.html" \
  -H "x-api-key: sc_your_api_key_here"

Rumble on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Rumble API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

SearchSearch Rumble videos Channel VideosList videos for a Rumble channel VideoGet a Rumble video Video TranscriptGet a Rumble video transcript Video CommentsList top-level comments on a Rumble video

Comparison

How does SocialCrawl compare to DIY scraping for Rumble data?

Same Rumble data, two very different paths. Auth, rate limits, schema, and cost, side by side.

Feature	SocialCrawl	DIY scraping
Setup	Sign up and send one GET request	Build proxies, headless browsers, and HTML parsers first
Authentication	One x-api-key header	None, but you handle blocks and bot detection yourself
Response schema	Unified JSON shared across 64 platforms	Raw HTML you parse and normalize yourself
Pricing	1 credit per request (10 for transcripts); 100 free credits	Proxy and server costs plus ongoing engineering hours
Data coverage	Search, channel uploads, video details, transcripts, comments	Whatever your parser extracts, transcripts are especially fiddly
Maintenance	SocialCrawl absorbs Rumble markup changes upstream	Your scraper breaks whenever Rumble changes its pages

Setup

SocialCrawl

DIY scraping

Build proxies, headless browsers, and HTML parsers first

Authentication

SocialCrawl

One x-api-key header

DIY scraping

None, but you handle blocks and bot detection yourself

Response schema

SocialCrawl

Unified JSON shared across 64 platforms

DIY scraping

Raw HTML you parse and normalize yourself

Pricing

SocialCrawl

1 credit per request (10 for transcripts); 100 free credits

DIY scraping

Proxy and server costs plus ongoing engineering hours

Data coverage

SocialCrawl

Search, channel uploads, video details, transcripts, comments

DIY scraping

Whatever your parser extracts, transcripts are especially fiddly

Maintenance

SocialCrawl

SocialCrawl absorbs Rumble markup changes upstream

DIY scraping

Your scraper breaks whenever Rumble changes its pages

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

How do I scrape Rumble data with an API?

SocialCrawl exposes 5 Rumble endpoints: keyword search, channel videos, video details, video transcript, and video comments. Send a GET request with your x-api-key and a query, handle, or video URL; normalized JSON comes back in one call.

Does Rumble have an official public data API?

No. Rumble offers creator-facing tools but no public REST API for reading search results, channel uploads, or comments. SocialCrawl fills that gap by reading publicly visible Rumble pages through our upstream provider and returning the data as structured JSON.

Is there a Rumble data API?

Yes. SocialCrawl is the Rumble data API: 5 REST endpoints for keyword search, channel uploads, video details, transcripts, and comments, all returned as unified JSON. There is no official public Rumble data API for reading arbitrary public data, so the alternative is a scraper you build and maintain yourself. SocialCrawl handles the upstream fetching and normalization; standard calls cost 1 credit and transcripts are premium at 10 credits, with 100 free credits to start.

What Rumble endpoints does SocialCrawl offer?

5 endpoints: Search, Channel Videos, Video, Video Transcript, and Video Comments.

How much does the Rumble API cost?

Search, channel videos, video details, and comments each cost 1 credit per request (standard tier). The transcript endpoint is premium at 10 credits, and if a video has no captions, transcript returns null and no credits are deducted. New accounts get 100 free credits, no card required.

Is scraping Rumble data legal?

SocialCrawl reads only publicly visible Rumble data: public videos, channels, view counts, and comments. You are responsible for complying with Rumble's Terms of Service and any data protection regulations that apply to your specific use case. SocialCrawl operates under a documented GDPR legitimate-interest framework: public, logged-out data only, no credential use, short-lived caches (2 to 30 minutes) with no persistent store, and a public opt-out channel for anyone whose public info appears in responses. Full details: socialcrawl.dev/legal/public-data-notice.

What can I build with the Rumble API?

Media monitoring across alternative video platforms, creator analytics dashboards that put Rumble next to YouTube and Twitch, misinformation and narrative research, and comment-level sentiment analysis. The unified schema means your YouTube parsing code handles Rumble responses too.

What is the best Rumble scraper API?

SocialCrawl is the most complete Rumble scraper API: 5 endpoints covering search, channel uploads, video details, transcripts, and comments. Standard calls cost 1 credit each; transcripts are premium at 10 credits. 100 free credits on signup, no card. Rumble has no public read API, so the alternative is a DIY scraper you maintain yourself.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Read the Rumble API reference in the docs

🤖 AI agent or LLM? Read this page as markdown