/bitchute/videos

POST /api/bitchute/videos

Price: 1 credit

Get BitChute Video

How to use it

Get one BitChute video by its 12-character id or its bitchute.com/video URL, with description, hashtags, view, like and dislike counts, and the uploading channel. A channel id passed here is not found.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• video string required — BitChute video id or video URL (examples: "FBQ4f8ZUY075", "https://www.bitchute.com/video/FBQ4f8ZUY075/"; minLength: 1)

Response

• @type string (default: "BitchuteVideo")
• id string required
• url string required
• description string nullable
• hashtags array (default: [])
• published_at integer nullable
• duration_seconds integer nullable
• image string nullable
• view_count integer nullable
• like_count integer nullable
• dislike_count integer nullable
• channel object nullable
  • @type string (default: "BitchuteVideoChannel")
  • id string required
  • name string nullable
  • url string nullable
  • image string nullable
  • subscriber_count integer nullable
  • created_at integer nullable
  • last_video_published_at integer nullable
• profile_id string nullable
• category_id string nullable
• sensitivity_id string nullable
• state_id string nullable
• rumble_id string nullable
• is_discussable boolean nullable
• show_comments boolean nullable
• show_rantrave boolean nullable
• show_adverts 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 — Video not found. Check the video id or URL. 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.