Skip to main content
Version: 1.0.0

Rumble Advertising Center API

The Rumble Advertising Center API allows programmatic access to your advertising data.

Features​

  • Query advertising statistics
  • More coming soon

Pagination​

This API uses cursor pagination to handle paging long lists of data. The cursor represents the current location when traversing the list. The first request to an endpoint should be made without a cursor. The response should include a next_cursor and a prev_cursor to access the next and previous pages. Provide the appropriate cursor on the next request to receive the next page of data. The response will also provide URLs when applicable.

Here's an example response:

{
  "data": [...],
  "pagination": {
    "path": "https://ads.rumble.com/api/v1/example",
    "per_page": "1000"
    "next_cursor": "ABCD",
    "next_page_url": "https://ads.rumble.com/api/v1/example?cursor=ABCD"
    "prev_cursor": "EFGH",
    "prev_page_url": "https://ads.rumble.com/api/v1/example?cursor=EFGH"
  }
}

You can also customize the page size with the per_page parameter.

Rate Limiting​

Requests are limited on a per minute basis. The default limit is 120 requests per minute, although this can vary by account.

You can see your limit and remaining requests by inspecting the response headers:

X-RateLimit-Limit: 120
X-RateLimit-Remaining: 60

Caching​

Responses may be cached for a period of time. Repeating the same request before the time has expired will result in the same response. You can see the duration a response is cached for by inspecting the response headers:

Cache-Control: max-age=5

Authenticating requests​

To authenticate requests, include an Authorization header with the value "Bearer {YOUR_AUTH_KEY}". This API is currently in limited release, so please contact your Rumble Ads representative to receive an API key.

Coming soon: You will be able to generate an API key by visiting your profile.

Authentication​

Security Scheme Type:

http

HTTP Authorization Scheme:

bearer