Rumble Video details API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Fetch one Rumble video from its page url, with title, uploader, views, votes, comment count, category, embed link and earnings data where Rumble shows it. Comment text is not included, and the video file is not downloaded.
Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.
Please help me write a data collection script with the EveryInfra Rumble Video details endpoint (rumble/video).
Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to rumble and action to video, and put the parameters inside params.
- Required parameters:
- url: Specifies a Rumble channel URL for profile and user_posts, or a video URL for video and comments.
- Returns one object. Main fields: id, url, title, author_name, author_url, author_followers, author_verified, view_count, like_count, dislike_count, vote_score, comment_count; 24 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=rumble.
- Example request body:
{
"platform": "rumble",
"action": "video",
"params": {
"url": "https://rumble.com/v7de1j2-coffee-and-justice-fafo-buffet.html"
}
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | rumble | Platform identifier, fixed value. |
action | body | string | Yes | video | Capability identifier, fixed value. |
url | body.params | Not declared | Yes | - | Specifies a Rumble channel URL for profile and user_posts, or a video URL for video and comments. For comments, it parses comments and replies from the video detail page rather than serving as a standalone comment search. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "rumble",
"action": "video",
"params": {
"url": "https://rumble.com/v7de1j2-coffee-and-justice-fafo-buffet.html"
}
}'[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.
{
"id": "req_…",
"platform": "rumble",
"action": "video",
"results": {
"id": …,
"url": …,
"title": …,
"author_name": …,
"author_url": …,
"author_followers": …,
"author_verified": …,
"view_count": …,
"like_count": …,
"dislike_count": …,
"vote_score": …,
"comment_count": …,
"duration_seconds": …,
"duration_sec": …,
"thumbnail_url": …,
"is_short": …,
"is_live": …,
"is_monetized": …,
"revenue": …,
"watching_now": …,
"tags": …,
"posted_at": …,
"category": …,
"embed_url": …,
"platform": …
},
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
id | The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms. |
url | Link to the record on the platform. |
title | Title. null when the platform has no titles (for example text-only posts). |
author_name | Author's display name. |
author_url | Link to the author's profile on the platform. |
author_followers | Keeps the platform's own meaning |
author_verified | Keeps the platform's own meaning |
view_count | Views or plays. null means not disclosed, not 0. |
like_count | Likes. null means the platform or this capability does not disclose it; it is not 0. |
dislike_count | Keeps the platform's own meaning |
vote_score | Keeps the platform's own meaning |
comment_count | Comments. null means not disclosed, not 0. |
duration_seconds | Duration in seconds. null for content that is not video or audio. |
duration_sec | Keeps the platform's own meaning |
thumbnail_url | Thumbnail link, lower resolution than image_url. |
is_short | Keeps the platform's own meaning |
is_live | Keeps the platform's own meaning |
is_monetized | Keeps the platform's own meaning |
revenue | Keeps the platform's own meaning |
watching_now | Keeps the platform's own meaning |
tags | Array of tags. An empty array, not null, when there are none. |
posted_at | Publish time in ISO 8601, UTC (for example 2026-08-07T12:34:56+00:00). Non-standard strings from the platform are passed through as is, so parse defensively. null means the platform does not disclose it. |
category | Category name in the platform's own taxonomy, not normalized across platforms. |
embed_url | Keeps the platform's own meaning |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
- 422
- Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
- 402
- Insufficient balance. Top up first.
- 429
- The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
- 503
- Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
- 200 empty
- The request completed without data and is not charged (billing.reason = empty_result_refunded).