List comments on a Rumble video · Rumble API
Returns top-level comments on a Rumble video by URL.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/rumble/videos/comments?url= \ -H "Authorization: Bearer $UNIFAPI_KEY"
Parameters
- urlqueryrequired
- Link to the Rumble video.
- The parameter for this Rumble operation. Use the URL-visible slug or id described in the docs.
This operation is part of the Rumble API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Rumble public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Pull public Rumble comment threads for sentiment, moderation, or audience-research agents.
- Collect top-level discussion around a post while preserving pagination and billing metadata.
- Give an AI agent a stable Rumble data source without building a per-platform integration.
- Normalize Rumble responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- List-style responses return `data` as an array of top-level records plus optional `pagination` for continuation tokens or cursors.
- The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
- If the workspace balance cannot cover every result, the response can be truncated and `billing.truncated_due_to_balance` tells the caller why.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields on each record in data
A successful List comments on a Rumble video call returns data as an array; each record carries these fields.
- idstring | null
- Stable identifier for the comment.
- textstring | null
- Comment text.
- created_atnumber | null
- ISO-8601 timestamp when the comment was published. Unix seconds.
- published_time_textstring | null
- Human-readable relative publish time when available.
- like_countnumber | null
- Like count on the comment when available.
- dislike_countnumber | null
- Dislike count on the comment when available.
- reply_countnumber | null
- Direct reply count for the comment thread when available.
- authorobject | null
- Comment author.
More Rumble operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
List videos from a Rumble channel
Returns the channel profile with its videos and Shorts for a Rumble channel URL. Paginate with `cursor`. Returns `not_found` when the channel does not exist.
Search Rumble
Searches Rumble by keyword and returns matching videos, Shorts, channels, playlists and live streams. Paginate with `cursor`.
Get a Rumble video by URL
Returns one Rumble video by URL: title, channel, duration, views, votes and playback URLs. Returns `not_found` when the video does not exist.
Get the captions of a Rumble video
Returns the captions of a Rumble video by URL when the video has them. Returns `not_found` when the video does not exist.