/rumble/videos/search

POST /api/rumble/videos/search

Price: 20 credits

Search Rumble Videos

How to use it

Search Rumble videos by keyword, by relevance, date, views or rumbles, optionally limited to an upload window and a short or long length band. Rumble serves at most 50 pages of 25 per query, so narrow the query or filters to reach older matches.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Search query (examples: "news"; minLength: 1)
• count integer required — Max result count (examples: 25; min: 1; max: 1250)
• sort string — Result order: relevance, newest, most viewed, or most rumbles (upvotes) (default: "relevance"; one of: "relevance", "date", "views", "rumbles")
• upload_date string nullable — Only videos uploaded within this window (one of: "today", "this-week", "this-month", "this-year")
• duration string nullable — Video length band (one of: "short", "long")

Response

• @type string (default: "RumbleVideoCard")
• id string required
• alias string nullable
• url string required
• image string nullable
• duration_seconds integer nullable
• published_at integer nullable
• view_count integer nullable
• comment_count integer nullable
• like_count integer nullable
• dislike_count integer nullable
• repost_count integer nullable
• tags array (default: [])
• width integer nullable
• height integer nullable
• is_live boolean nullable
• is_short boolean nullable
• is_age_restricted boolean nullable
• is_monetized boolean nullable
• visibility string nullable
• channel object nullable
  • @type string (default: "RumbleVideoChannel")
  • name string required
  • alias string nullable
  • url string nullable
  • id string nullable
  • image string nullable
  • follower_count integer nullable
  • is_verified boolean 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 — The entity was not found, or a precondition failed 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.