# Rumble Email Scraper (`leads-scraper/rumble-email-scraper`) Actor

Rumble Email Scraper SD - Rumble Email Scraper is a lead generation tool that extracts leads with public contact emails, account names and profile URLs from Rumble results by keyword, location and email domain - Rumble email extractor.

- **URL**: https://apify.com/leads-scraper/rumble-email-scraper.md
- **Developed by:** [Leads Scraper](https://apify.com/leads-scraper) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.49 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### Rumble Email Scraper

The **Rumble Email Scraper** finds publicly indexed contact emails for Rumble channels and creators, and turns them into a clean, structured dataset you can export as JSON, CSV or Excel.

Rumble has become the home of independent news channels, outdoor and hunting creators, firearms and gear reviewers, faith-based broadcasters, motorsport channels and political commentators. Many of them publish a business inquiry address right in their channel description.

The Rumble Email Scraper collects exactly those addresses. It runs a keyword-driven Google search against `rumble.com`, parses each result block, and extracts any email that matches the domains you asked for.

This is a search-driven contact discovery tool, not a login tool. The Rumble Email Scraper never signs in to Rumble, never opens the Rumble website, and never touches private data — every lead comes from a page Google has already indexed publicly.

#### Who this Rumble email extractor is for

Sponsorship teams, affiliate managers, media buyers, agencies, recruiters and researchers who need Rumble creator emails in bulk rather than one channel at a time.

If you have ever opened forty Rumble channel pages in forty tabs looking for a business address, this Rumble contact scraper replaces that afternoon with a single run.

***

### Key Features of the Rumble Email Scraper

Everything below is genuinely implemented in the Rumble Email Scraper — no roadmap items, no marketing filler.

| Feature | What it does |
|---|---|
| Google SERP data collection | Builds `site:rumble.com` queries and fetches result pages through the Apify GOOGLE\_SERP proxy |
| Query expansion | Runs base, quoted and `intitle:` variants plus one variant per query modifier, so you beat Google's per-query result cap |
| Domain filtering | Keeps only emails ending in the domains you list (`@gmail.com`, `@yahoo.com` by default) |
| Global deduplication | One row per unique email across every query, every page, every keyword |
| Email normalisation | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, zero-width characters and the full-width `＠` sign |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Soft-wrap repair | Drops a hit that is only the tail of another email in the same result block |
| Concurrency control | An `asyncio` worker pool runs several queries in parallel with a shared stop signal |
| Retry logic | Up to 3 attempts per page, exponential backoff, a fresh proxy session per request |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, never counted as empty |
| Resumable state | Progress is stored in the key-value store and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING` |
| Structural parser | Locates the `<h3>` title and the smallest surrounding block instead of depending on Google's CSS class names |
| Whole-page fallback | If Google's markup changes, the crawler degrades to "emails without account details" rather than "no emails" |
| Streaming dataset writes | Every lead is pushed to the Apify dataset the moment it is found |

***

### How the Rumble Email Scraper Works

The Rumble Email Scraper pipeline is deliberately simple, which is why it is robust.

1. **Read the input.** Keywords, optional location, email domains and limits.
2. **Build queries.** Each keyword is combined with each domain into a `site:rumble.com` search — for example `site:rumble.com hunting channel "@gmail.com" "Montana"`.
3. **Expand queries.** With `expandQueries` on, the Rumble Email Scraper also runs quoted and `intitle:` phrasings plus one variant per modifier. Base queries always run first.
4. **Fetch pages.** Result pages are requested asynchronously with `aiohttp` through the Apify GOOGLE\_SERP proxy, with pagination up to `maxPagesPerQuery`.
5. **Parse each block.** The parser finds the result title, then the smallest surrounding block, and reads the title, site label and snippet as metadata.
6. **Extract and filter emails.** A domain-filtered regex pulls addresses out of the block text.
7. **Deduplicate and store.** New emails are pushed straight to the dataset; duplicates are discarded.

There is no browser, no JavaScript rendering, no authentication and no cookies anywhere in that chain. That is what keeps the Rumble Email Scraper cheap to run and easy to reason about.

***

### What Data Does the Rumble Email Scraper Extract

Every dataset item produced by the Rumble Email Scraper carries the same 14 fields, so your output schema never changes between runs. That makes the Rumble Email Scraper easy to map into a CRM or a spreadsheet template once and reuse forever.

| Field | Meaning |
|---|---|
| `network` | Platform name |
| `keyword` | The keyword that produced the lead |
| `query` | The exact Google query used |
| `title` | Raw result title |
| `accountName` | Account label Google prints |
| `fullName` | Display name parsed from a profile-style title; empty for video captions |
| `username` | URL-safe channel handle when Rumble exposes one; otherwise `null` |
| `profileUrl` | Canonical channel URL when a handle is known; otherwise empty |
| `url` | Direct Rumble link when exposed, else the profile URL |
| `description` | Bio or caption snippet, cleaned of labels and engagement counters |
| `email` | Lower-cased email address |
| `emailDomain` | The matched domain, e.g. `@gmail.com` |
| `possiblyTruncated` | `true` when Google's snippet ellipsis touched the email |
| `foundAt` | ISO 8601 UTC timestamp |

***

### Input Fields

Nine fields control the Rumble Email Scraper. Only `keywords` is required; every other field has a sensible default.

| Field | Type | Default | Description |
|---|---|---|---|
| `keywords` | array (required) | `["creator", "channel"]` | Search terms: niche, job title, industry |
| `location` | string | `""` | Optional location phrase added to every query |
| `customDomains` | array | `["@gmail.com", "@yahoo.com"]` | Only emails on these domains are kept; the `@` is optional |
| `maxEmails` | integer 1–10000 | `20` | Stop after this many unique emails |
| `countryCode` | string | `""` | Two-letter country for the search proxy (US, GB, DE…) |
| `expandQueries` | boolean | `true` | Search each keyword × domain pair in several phrasings |
| `queryModifiers` | array | `["business inquiries", "email", "contact", "sponsorship"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1–50 | `30` | Pagination cap per query |
| `maxConcurrency` | integer 1–20 | `5` | Parallel queries |

#### JSON input example

```json
{
  "keywords": ["hunting channel", "gear review", "outdoor creator"],
  "location": "Montana",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 300,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["business inquiries", "email", "contact", "sponsorship"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output Schema and Dataset Export

The Rumble Email Scraper writes results to the Apify dataset as they are found, so you can watch leads arrive mid-run and export at any point.

#### JSON output example

```json
{
  "network": "Rumble",
  "keyword": "hunting channel",
  "query": "site:rumble.com hunting channel \"@gmail.com\" \"Montana\"",
  "title": "Backcountry Ridge (@backcountryridge) - Rumble",
  "accountName": "backcountryridge",
  "fullName": "Backcountry Ridge",
  "username": "backcountryridge",
  "profileUrl": "https://rumble.com/c/backcountryridge",
  "url": "https://rumble.com/c/backcountryridge",
  "description": "Weekly backcountry hunts, elk gear tests and field reviews. Sponsorship and business inquiries: backcountry.ridge.media@gmail.com",
  "email": "backcountry.ridge.media@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:41:12.338Z"
}
```

Export the dataset as JSON, CSV, XLSX or XML from the Apify console, or pull it through the API into your CRM.

***

### How to Run It

1. Open the Rumble Email Scraper on Apify and click **Try for free**.
2. Replace the default keywords with the Rumble niches you actually want — `firearms review`, `homestead vlog`, `motorsport channel`.
3. Add the email domains you care about. Narrow domain lists give cleaner results than broad ones.
4. Optionally set a `location` and a `countryCode` to bias the search results regionally.
5. Set `maxEmails` to the size of the list you need and start the run.
6. Watch the live log: it reports pages fetched, blocked pages, retries and emails per page.
7. Export the dataset, or chain the Rumble Email Scraper into a workflow with the Apify API.

#### Tips for a better yield

Give the Rumble Email Scraper two or three tightly related keywords per run rather than one generic word. `creator` is broad; `outdoor gear reviewer` is a query that actually converts.

Leave `expandQueries` on. It is the single biggest factor in how many Rumble creator emails a run returns.

If a niche is exhausted, change the domain list instead of the keyword — the same channels often publish addresses on different providers.

***

### Use Cases for the Rumble Email Scraper

Teams reach for the Rumble Email Scraper whenever a workflow starts with "find every Rumble channel that…".

| Use case | How the Rumble Email Scraper helps |
|---|---|
| Sponsorship outreach | Build a list of Rumble channels in a vertical and pitch them directly |
| Affiliate recruitment | Find outdoor, firearms, survival and gear channels that already review products |
| Influencer marketing | Assemble a creator shortlist with bios, handles and contact addresses in one dataset |
| Media and PR | Reach independent news and commentary channels for interviews and press placements |
| Agency prospecting | Sell editing, thumbnails, monetisation or channel management to active creators |
| Market research | Map who is publishing in a Rumble niche and how they describe themselves |
| CRM enrichment | Append profile URLs and bio snippets to contacts you already hold |
| Event and podcast booking | Source guests from a specific topic area with a working contact route |

***

### Why Choose This Actor

Rumble does not offer a public creator directory with contact details, and manual lookups do not scale past a couple of dozen channels.

This Rumble Email Scraper automates the boring half of Rumble lead generation: the searching, the pagination, the copy-pasting and the deduplication. You keep the judgement calls; the crawler does the typing.

Because the Rumble Email Scraper parses structurally rather than by CSS class name, and because there is a whole-page fallback, layout changes on Google's side degrade quality instead of breaking the run.

It also plays well with the rest of this family. Creators rarely live on one platform — pair the Rumble Email Scraper with the [YouTube Email Scraper](https://apify.com/leads-scraper/youtube-email-scraper) for the same niches on YouTube, and with the [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) or [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) for their live-streaming presence.

For the social layer around a Rumble channel, the [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) and [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) usually surface the same people with different addresses, and the [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) is strong for the communities those channels grow in.

***

### Limitations

These are real constraints on the Rumble Email Scraper, and worth reading before your first run.

- **Only publicly indexed emails.** The Rumble Email Scraper finds addresses Google has already crawled. If a creator never published an email, it will not appear.
- **Google's result cap.** A single query returns roughly 300 results maximum. That is precisely why query expansion exists — leave it on.
- **`possiblyTruncated`.** When Google's snippet ellipsis touches an address, the row is flagged `true`. Verify those before sending anything.
- **Apify GOOGLE\_SERP proxy required.** The Rumble Email Scraper cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are limited to 100 emails per run; paid plans are uncapped.
- **`username` and `profileUrl` availability.** These are populated only when Rumble exposes a handle in Google's result. When Google shows only a display name, the row still has `accountName` and `fullName` but an empty `username` and `profileUrl`. That is a Google limitation, not a bug.
- **Variable yield.** Results depend on keywords, domains and location. No volume is guaranteed.

***

### Example: a full run

Here is what one Rumble Email Scraper run looks like end to end. Input: three keywords, two domains, expansion on, `maxEmails: 300`.

The Rumble Email Scraper builds base queries first (`site:rumble.com gear review "@gmail.com"`), then quoted and `intitle:` variants, then one variant per modifier — `business inquiries`, `email`, `contact`, `sponsorship`.

Five queries run concurrently, each paginating until it runs dry or hits `maxPagesPerQuery`. Emails are normalised, filtered against your domain list, deduplicated globally and streamed to the dataset until the 300th unique address stops every worker.

Blocked or failed queries are re-queued once at the end, so a temporary CAPTCHA does not silently cost you a keyword.

***

### Related Actors

The Rumble Email Scraper is part of a family of contact-discovery Actors that share this engine and output schema.

| Actor | What it collects |
|---|---|
| [Rumble Email and Phone Number Scraper](https://apify.com/leads-scraper/rumble-email-and-phone-number-scraper) | Emails and phone numbers from Rumble |
| [Rumble Phone Number Scraper](https://apify.com/leads-scraper/rumble-phone-number-scraper) | Public phone numbers from Rumble |
| [Behance Email Scraper](https://apify.com/leads-scraper/behance-email-scraper) | Public contact emails from Behance |
| [Bigo Live Email Scraper](https://apify.com/leads-scraper/bigo-live-email-scraper) | Public contact emails from Bigo Live |
| [Bluesky Email Scraper](https://apify.com/leads-scraper/bluesky-email-scraper) | Public contact emails from Bluesky |
| [Bumble Email Scraper](https://apify.com/leads-scraper/bumble-email-scraper) | Public contact emails from Bumble |
| [Clubhouse Email Scraper](https://apify.com/leads-scraper/clubhouse-email-scraper) | Public contact emails from Clubhouse |
| [Dailymotion Email Scraper](https://apify.com/leads-scraper/dailymotion-email-scraper) | Public contact emails from Dailymotion |
| [DeviantArt Email Scraper](https://apify.com/leads-scraper/deviantart-email-scraper) | Public contact emails from DeviantArt |
| [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) | Public contact emails from Discord |
| [Dribbble Email Scraper](https://apify.com/leads-scraper/dribbble-email-scraper) | Public contact emails from Dribbble |
| [Facebook Email Scraper](https://apify.com/leads-scraper/facebook-email-scraper) | Public contact emails from Facebook |
| [Goodreads Email Scraper](https://apify.com/leads-scraper/goodreads-email-scraper) | Public contact emails from Goodreads |
| [Hinge Email Scraper](https://apify.com/leads-scraper/hinge-email-scraper) | Public contact emails from Hinge |
| [Instagram Email Scraper](https://apify.com/leads-scraper/instagram-email-scraper) | Public contact emails from Instagram |
| [KakaoTalk Email Scraper](https://apify.com/leads-scraper/kakaotalk-email-scraper) | Public contact emails from KakaoTalk |
| [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) | Public contact emails from Kick |
| [Lemon8 Email Scraper](https://apify.com/leads-scraper/lemon8-email-scraper) | Public contact emails from Lemon8 |
| [Likee Email Scraper](https://apify.com/leads-scraper/likee-email-scraper) | Public contact emails from Likee |
| [LINE Email Scraper](https://apify.com/leads-scraper/line-email-scraper) | Public contact emails from LINE |
| [LinkedIn Email Scraper](https://apify.com/leads-scraper/linkedin-email-scraper) | Public contact emails from LinkedIn |
| [Mastodon Email Scraper](https://apify.com/leads-scraper/mastodon-email-scraper) | Public contact emails from Mastodon |
| [Medium Email Scraper](https://apify.com/leads-scraper/medium-email-scraper) | Public contact emails from Medium |
| [Mixcloud Email Scraper](https://apify.com/leads-scraper/mixcloud-email-scraper) | Public contact emails from Mixcloud |
| [Patreon Email Scraper](https://apify.com/leads-scraper/patreon-email-scraper) | Public contact emails from Patreon |
| [Pinterest Email Scraper](https://apify.com/leads-scraper/pinterest-email-scraper) | Public contact emails from Pinterest |
| [Quora Email Scraper](https://apify.com/leads-scraper/quora-email-scraper) | Public contact emails from Quora |
| [Reddit Email Scraper](https://apify.com/leads-scraper/reddit-email-scraper) | Public contact emails from Reddit |
| [Snapchat Email Scraper](https://apify.com/leads-scraper/snapchat-email-scraper) | Public contact emails from Snapchat |
| [SoundCloud Email Scraper](https://apify.com/leads-scraper/soundcloud-email-scraper) | Public contact emails from SoundCloud |
| [Substack Email Scraper](https://apify.com/leads-scraper/substack-email-scraper) | Public contact emails from Substack |
| [Telegram Email Scraper](https://apify.com/leads-scraper/telegram-email-scraper) | Public contact emails from Telegram |
| [Threads Email Scraper](https://apify.com/leads-scraper/threads-email-scraper) | Public contact emails from Threads |
| [TikTok Email Scraper](https://apify.com/leads-scraper/tiktok-email-scraper) | Public contact emails from TikTok |
| [Tinder Email Scraper](https://apify.com/leads-scraper/tinder-email-scraper) | Public contact emails from Tinder |
| [Tumblr Email Scraper](https://apify.com/leads-scraper/tumblr-email-scraper) | Public contact emails from Tumblr |
| [Twitch Email Scraper](https://apify.com/leads-scraper/twitch-email-scraper) | Public contact emails from Twitch |
| [Vimeo Email Scraper](https://apify.com/leads-scraper/vimeo-email-scraper) | Public contact emails from Vimeo |
| [VK Email Scraper](https://apify.com/leads-scraper/vk-email-scraper) | Public contact emails from VK |
| [WeChat Email Scraper](https://apify.com/leads-scraper/wechat-email-scraper) | Public contact emails from WeChat |
| [Weibo Email Scraper](https://apify.com/leads-scraper/weibo-email-scraper) | Public contact emails from Weibo |
| [X Email Scraper](https://apify.com/leads-scraper/x-email-scraper) | Public contact emails from X |

### FAQ

#### What is the Rumble Email Scraper?

An Apify Actor that extracts publicly indexed contact emails for Rumble channels and creators from Google search results and writes them to a structured dataset.

#### Does the Rumble Email Scraper log in to Rumble?

No. It does not log in, does not use a Rumble API, and does not open the Rumble website. It reads Google search results only.

#### Where do the emails come from?

Titles, snippets and site labels in Google's public index — usually a business inquiry address a creator put in their channel description. The Rumble Email Scraper reads nothing else.

#### Can I control which email providers are returned?

Yes. `customDomains` filters the Rumble Email Scraper's extraction step. The defaults are `@gmail.com` and `@yahoo.com`, and you can list any domains you like, with or without the `@`.

#### Why is `username` empty on some rows?

Google sometimes prints only a display name for a result. When no handle is exposed, `username` is `null` and `profileUrl` is empty, while `accountName` and `fullName` are still filled.

#### What does `possiblyTruncated: true` mean?

Google's snippet ellipsis touched the address, so it may be cut off. Treat those rows as unverified and check them before outreach.

#### How many Rumble creator emails will one run return?

It depends entirely on keywords, domains and location — no volume is guaranteed. Free Apify plans stop at 100 emails per run; paid plans are uncapped.

#### Do I need a proxy?

Yes. The Rumble Email Scraper requires the Apify GOOGLE\_SERP proxy and cannot run without Apify proxy credentials.

#### Should I leave query expansion on?

Almost always. Google caps a single query at roughly 300 results, and expansion is how the Actor works around that ceiling.

#### Is the Rumble Email Scraper affiliated with Rumble?

No. It is an independent Apify Actor and is not endorsed by or connected to Rumble.

#### Can I run the Rumble Email Scraper on a schedule?

Yes. Use Apify Schedules to run it nightly or weekly and append fresh leads to the same dataset.

#### What happens if the run is interrupted?

State is stored in the key-value store and saved on `PERSIST_STATE`, `MIGRATING` and `ABORTING`, so a migrated run resumes rather than restarting.

#### Are duplicates removed?

Yes. Deduplication is global — one row per unique email across every query and every page in the run.

#### Can I export to CSV or push straight to a CRM?

Yes. Export the Rumble Email Scraper dataset as JSON, CSV, XLSX or XML, or read it through the Apify API and load it into your own pipeline.

#### Does the output schema ever change?

No. Every item the Rumble Email Scraper writes contains the same 14 fields, which makes downstream mapping stable.

***

### Leave a review

If the Rumble Email Scraper saved you time, please leave a star rating and a short review on
the Actor page.

Reviews are how other buyers judge whether a tool works, and they tell us which features to
build next.

If something did not work, email <neurodata.apify@gmail.com>
instead - bugs get fixed faster than they get complained about.

### Support

Questions about the Rumble Email Scraper, feature requests, or need a custom build? Email **neurodata.apify@gmail.com**.

Not affiliated with, endorsed by, or officially connected to Rumble. Use the data you collect in line with applicable privacy and anti-spam law.

# Actor input Schema

## `keywords` (type: `array`):

Search terms describing the Rumble accounts you want (niche, job title, industry).

## `location` (type: `string`):

Optional location phrase added to every query (e.g. "New York").

## `customDomains` (type: `array`):

Only emails ending with one of these domains are collected. With or without the leading @. Each domain is searched separately, so more domains means more results but a longer run - remove some for a faster, narrower search, or add your own (e.g. @company.com).

## `maxEmails` (type: `integer`):

Stop once this many unique emails have been collected.

## `countryCode` (type: `string`):

Two-letter country code for the search proxy (e.g. US, GB, DE). Empty for any.

## `expandQueries` (type: `boolean`):

Search each keyword x domain pair with several phrasings. Recommended - Google caps a single query at ~300 results.

## `queryModifiers` (type: `array`):

Extra words combined with each keyword when Expand queries is on. Tuned for Rumble.

## `maxPagesPerQuery` (type: `integer`):

Google rarely returns more than ~30 pages for one query.

## `maxConcurrency` (type: `integer`):

How many queries run in parallel.

## Actor input object example

```json
{
  "keywords": [
    "creator",
    "channel"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "business inquiries",
    "email",
    "contact",
    "sponsorship"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Records produced by Rumble Email Scraper, stored in the run's default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "creator",
        "channel"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "business inquiries",
        "email",
        "contact",
        "sponsorship"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leads-scraper/rumble-email-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "keywords": [
        "creator",
        "channel",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "business inquiries",
        "email",
        "contact",
        "sponsorship",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("leads-scraper/rumble-email-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "keywords": [
    "creator",
    "channel"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "business inquiries",
    "email",
    "contact",
    "sponsorship"
  ]
}' |
apify call leads-scraper/rumble-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/rumble-email-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/mMqVDiJ1rVUoTtdDJ/builds/YcO54RgAiHTIwzmp7/openapi.json