/rumble/videos

POST /api/rumble/videos

Price: 10 credits

Get Rumble Video

How to use it

Get one Rumble video from its rumble.com URL, its embed URL, the v-prefixed id in the URL, or the numeric id that video search and channel videos return. Vote and follower counts are Rumble's rounded display figures; the view count is exact.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• video string required — Rumble video URL, rumble.com/embed URL, the v-prefixed video id from the URL, or the numeric video id returned by search (examples: "https://rumble.com/v7farey-the-worlds-okayest-gun-show.html", "v7farey", "445303636"; minLength: 1)

Response

• @type string (default: "RumbleVideo")
• id string required
• alias string nullable
• embed_id string required
• url string nullable
• description string nullable
• author object nullable
  • @type string (default: "RumbleVideoAuthor")
  • name string required
  • alias string nullable
  • url string nullable
  • follower_count integer nullable
• channel_id string nullable
• creator_id string nullable
• duration_seconds integer nullable
• published_at integer nullable
• view_count integer nullable
• like_count integer nullable
• dislike_count integer nullable
• categories array (default: [])
• image string nullable
• images array (default: [])
• width integer nullable
• height integer nullable
• fps number nullable
• is_live boolean nullable
• is_live_placeholder boolean nullable
• moment_count integer nullable
• captions array (default: [])
  • @type string (default: "RumbleVideoCaption")
  • language string required
  • url string required
• media array (default: [])
  • @type string (default: "RumbleVideoMedia")
  • stream_format string required
  • quality string nullable
  • url string required
  • bitrate integer nullable
  • size_bytes integer nullable
  • width integer nullable
  • height integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Video not found. Check the Rumble URL or video id. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.