> Documentation index: https://docs.scrapier.io/llms.txt
> Auth: header `X-API-Key: <key>` · Base: https://api.scrapier.io/api/v2 · Synchronous; paginate with `cursor` ← `data.next_cursor`.

# Rumble Videos

Structured Rumble data: send `urls`. Single lookup, 1 credit per successful call.

`GET|POST https://api.scrapier.io/api/v2/rumble-video/` · 1 credit per successful call · Single lookup

## Overview

Call `GET /api/v2/rumble-video/` with `urls`. The results are in `data.video`. 1 optional parameter refines the call (see Parameters).

## Request

```bash
curl -G "https://api.scrapier.io/api/v2/rumble-video/" \
  -H "X-API-Key: YOUR_API_KEY" \
  --data-urlencode "urls=v7fr3se" \
  --max-time 210
```

```python
import requests

resp = requests.get(
    "https://api.scrapier.io/api/v2/rumble-video/",
    headers={"X-API-Key": "YOUR_API_KEY"},
    params={"urls": "v7fr3se"},
    timeout=210,
)
body = resp.json()
if not resp.ok:
    raise RuntimeError(body.get("error") or body.get("detail"))

print(body["data"]["video"])
```

POST with a JSON body works too (same parameters; the body is merged over the query string).

## Parameters

| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| `X-API-Key` (header) | string | yes | — | Your API key. |
| `urls` | string | yes | e.g. `v7fr3se` | Full Rumble watch URL or bare video id. One record, no pagination. |
| `use_proxy` | boolean | no | `true` | Route the request through Scrapier's residential proxy pool. Default: `true`. Leave as is unless support tells you otherwise. |
| `raw_data` | boolean | no | `false` | When true, the response carries the full raw upstream payload(s) the scraper received (GraphQL / JSON API bodies, HTML, embedded JSON-LD -- exactly as the platform returned them) under `raw_responses`, in place of the formatted items. When false (default) you get the formatted output. Pagination (`cursor` / `next_cursor`) works the same in both modes. |

## Response

HTTP 200. Results are in `data.video`. Sample from the live catalog, arrays trimmed to 3 items.

```json
{
  "success": true,
  "data": {
    "urls": "v7fr3se",
    "video": {
      "input_url": "https://rumble.com/v7fr3se",
      "success": true,
      "id": "v7fr3se",
      "title": "Ep 3996b - Did You See The Move That Was Made Against The [DS]?",
      "viewCountInt": 160818,
      "likeCount": 4400,
      "dislikeCount": 41,
      "channel": {
        "name": "X22 Report",
        "handle": "X22Report"
      }
    },
    "next_cursor": null
  }
}
```

## Response fields

| Field | Type | Example | Description |
|---|---|---|---|
| `urls` | string | `v7fr3se` |  |
| `video` | object | `{…}` | The results. |
| `next_cursor` | null | `null` | Pass back as `cursor` for the next page. `null` on the last page. |
| `video.input_url` | string | `https://rumble.com/v7fr3se` |  |
| `video.success` | boolean | `true` |  |
| `video.id` | string | `v7fr3se` |  |
| `video.title` | string | `Ep 3996b - Did You See The Move That Was Made…` |  |
| `video.viewCountInt` | integer | `160818` |  |
| `video.likeCount` | integer | `4400` |  |
| `video.dislikeCount` | integer | `41` |  |
| `video.channel` | object | `{…}` |  |

## Pagination

Single lookup: everything comes back in one call and `next_cursor` is always `null`.

## Errors

Failed calls are free. Branch on HTTP status; the message is in `error` (or `detail`). See https://docs.scrapier.io/errors.md

- **400** Bad input. The exact message varies by endpoint. `{"success":false,"error":"…"}`
- **402** Balance below the endpoint's price. `{"error":"Insufficient credits. Buy more to scrape more.","balance":1,"required":2}`
- **403** Invalid or unknown API key. `{"detail":"Authentication service unavailable or invalid API key."}`
- **429** Throttled — wait for Retry-After. `{"detail":"Request was throttled. Expected available in N seconds."}`
- **404** unknown slug · **503** busy (retry after `Retry-After`) · **5xx** upstream failure or timeout (retry with backoff).

## Notes

- The response data carries its own `success` field from the scraper. The outer `success` is what counts: an HTTP 200 with outer `success: true` is billed, even if the inner field says otherwise.

## Related

- [Rumble Channel Videos](https://docs.scrapier.io/api-reference/rumble/rumble-channel-videos.md): Structured Rumble data: send `handles`. Cursor-paginated, 1 credit per successful call.
- [Rumble Comments](https://docs.scrapier.io/api-reference/rumble/rumble-comments.md): Structured Rumble data: send `urls`. Single lookup, 1 credit per successful call.
- [Rumble Search](https://docs.scrapier.io/api-reference/rumble/rumble-search.md): Structured Rumble data: send `queries`. Cursor-paginated, 1 credit per successful call.
- [Rumble Transcript](https://docs.scrapier.io/api-reference/rumble/rumble-transcript.md): Structured Rumble data: send `urls`. Single lookup, 1 credit per successful call.
