Social platforms

Get a Rumble video by URL · Rumble API

GET/rumble/videos
$min $0.003

Returns one Rumble video by URL: title, channel, duration, views, votes and playback URLs. Returns `not_found` when the video does not exist.

Using ChatGPT, Claude Code or another client? See the setup steps

Request
curl https://api.unifapi.com/rumble/videos?url= \
  -H "Authorization: Bearer $UNIFAPI_KEY"

Parameters

urlqueryrequired
Link to the Rumble video.
The parameter for this Rumble operation. Use the URL-visible slug or id described in the docs.
Overview

This operation is part of the Rumble API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.

Use it when a workflow needs Rumble public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.

Common agent workflows

  • Fetch canonical public Rumble content for summarization, ranking, monitoring, or enrichment.
  • Attach engagement, author, media, and source metadata to an agent workflow.
  • Give an AI agent a stable Rumble data source without building a per-platform integration.
  • Normalize Rumble responses into the same UnifAPI envelope used across the catalog.
Response shape

Unified envelope, platform-native fields

  • Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
  • The operation has a 3 credits ($0.003) minimum charge, so `billing.records_charged` can be higher than the visible records returned.
  • A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.

Response status codes

200400401402404429500502503

Billing

This operation charges 1 credit per billable record, with a 3 credits ($0.003) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.

Errors and retries

Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.

Response fields

Fields in the data object

A successful Get a Rumble video by URL call returns one data object with these fields (12 of 19 shown — the docs list the full schema).

idstring | null
Rumble video identifier.
urlstring | null
Canonical public Rumble video URL.
titlestring | null
Video title.
descriptionstring | null
Video description text when available.
thumbnail_urlstring | null
Thumbnail image URL when available.
durationnumber | null
Video duration in seconds when available.
duration_formattedstring | null
Human-readable duration label when available.
published_atnumber | null
ISO-8601 publish timestamp when available. Unix seconds.
publish_date_textstring | null
Human-readable publish date label when available.
view_countnumber | null
View count when available.
like_countnumber | null
Like count when available.
dislike_countnumber | null
Dislike count when available.