> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/rumble/videos-comments>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/rumble/videos-comments.mdx>

---

# Rumble comments API

Pass a public Rumble video URL and get top-level comments with text, likes, dislikes, and authors — same Social Fetch envelope as video detail and transcripts.

`GET /v1/rumble/videos/comments` takes a required `url` query param (a public Rumble video link). On a found lookup, read `data.comments`, `data.video` (resolved id and canonical url), and `data.page`. Each top-level row can include `id`, `text`, `createdAt`, `publishedTimeText`, `likeCount`, `dislikeCount`, `replyCount`, and an `author` object (`displayName`, `handle`, `profileUrl`, `avatarUrl`). Branch on `data.lookupStatus` (`found` or `not_found`) before you write rows — HTTP 200 alone does not mean the video resolved.

Bill from `meta.creditsCharged`. This route lists top-level comments for one video URL; there is no separate Rumble comment-replies operation in the public API. Video metadata is `GET /v1/rumble/videos`. Spoken captions are `GET /v1/rumble/videos/transcript`. Same API key across the Rumble tag.

## Request

- **Endpoint:** `GET /v1/rumble/videos/comments`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by video URL
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/rumble/videos/comments/get)
- **Platform page:** [/platforms/rumble](https://www.socialfetch.dev/platforms/rumble)

## FAQ

### How do I list Rumble video comments via API?

Call GET /v1/rumble/videos/comments with your Social Fetch API key (x-api-key) and a public video url query param. Read data.lookupStatus, then data.comments, data.video, and data.page. See the API docs for parameters and examples.

### How much does the Rumble comments endpoint cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged — that field is the billing source of truth.

### What fields are in each Rumble comment?

Top-level rows can include id, text, createdAt, publishedTimeText, likeCount, dislikeCount, replyCount, and author (displayName, handle, profileUrl, avatarUrl). Always branch on data.lookupStatus before treating comments as present.

### What does data.lookupStatus mean on Rumble comments?

found means the video resolved and the comments list (which may be empty) is valid. not_found means the video could not be resolved; comments is empty and video is null. HTTP 200 alone does not mean you have a thread to store.

### Can I fetch nested replies on Rumble comments?

This route returns top-level comments and may include replyCount on each row. There is no separate public Social Fetch operation for Rumble comment reply threads. Use replyCount as a signal when you need volume, not as a nested reply tree.

### What URL formats does the Rumble comments API accept?

Public Rumble video URLs (watch-page links to a single video). Pass one url per request. Private or deleted videos resolve as not_found rather than a fake empty object.

### How is this different from the Rumble video detail endpoint?

GET /v1/rumble/videos returns title, channel, metrics, and captionTracks. GET /v1/rumble/videos/comments returns the top-level comment list for the same style of video URL. Call video detail for views and title; call comments when you need the thread text.

### Do I need a Rumble developer key to read video comments?

No. You authenticate to Social Fetch with an API key. The route reads public comment data; it does not act on behalf of a logged-in Rumble user.