# YouTube Email Scraper (`neuro-data/youtube-email-scraper`) Actor

YouTube Email Scraper SD - YouTube Email Scraper is a powerful tool that extracts public business inquiry emails, channel names, handles and channel URLs from YouTube results by keyword, niche and email domain - YouTube email extractor for sponsorship and creator outreach.

- **URL**: https://apify.com/neuro-data/youtube-email-scraper.md
- **Developed by:** [Neuro Data](https://apify.com/neuro-data) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.99 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## YouTube Email Scraper

### YouTube Email Scraper - Find Creator Business Inquiry Emails by Keyword

The **YouTube Email Scraper** is an Apify Actor that collects publicly indexed contact emails belonging to YouTube channels. You supply keywords; it returns a structured dataset of creator leads.

The YouTube Email Scraper works by running `site:youtube.com` searches through the Apify GOOGLE\_SERP proxy and parsing addresses out of the result blocks. That is the complete mechanism.

The YouTube Email Scraper does **not** log into YouTube, does **not** use the YouTube Data API and does **not** open youtube.com. No browser, no JavaScript rendering, no authentication, no cookies.

Everything the YouTube Email Scraper returns already exists in Google's public index: titles, snippets and site labels. If a creator wrote `business inquiries: me@gmail.com` in a channel description Google crawled, this Actor can surface it.

That makes it a **YouTube email extractor** built for sponsorship prospecting and creator contact discovery. You do not need a list of channel IDs to start - you start from a niche.

***

### Key Features

| Feature | What it does |
|---|---|
| Keyword-driven search | Start the YouTube Email Scraper from a niche or vertical, not from a list of channel URLs |
| Query expansion | Each keyword x domain pair runs as base, quoted, `intitle:` and one variant per modifier |
| Domain filtering | Only emails on the domains you list (`@gmail.com`, `@yahoo.com`, ...) are kept |
| Obfuscation handling | Understands `name [at] domain [dot] com`, `name (at) domain`, `name @ domain.com`, `domain .com`, zero-width characters and the full-width at sign |
| Junk filter | Rejects placeholders such as `email@`, `yourname@`, `test@`, `xxx@` and single-character locals |
| Boundary-correct matching | `@gmail.com` never matches inside `@gmail.company` or `@gmail.com.br` |
| Global deduplication | One row per unique email across every query and every page |
| Concurrency | 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 lives in the key-value store, keyed by a hash of your input |
| Fallback parser | If Google's markup changes, a run degrades to "emails without account details", not "no emails" |
| Live dataset writes | Each lead reaches the Apify dataset the moment it is found |
| Location targeting | An optional location phrase is appended to every query |

The YouTube Email Scraper parser locates each `<h3>` title, then the smallest surrounding block. It does **not** depend on Google's CSS class names, which is why the YouTube Email Scraper tolerates most SERP layout changes.

***

### How the YouTube Email Scraper Works

The YouTube Email Scraper pipeline is short, deterministic and auditable - every row stores the exact query that produced it.

1. **Read input.** Keywords, location, email domains and limits are validated.
2. **Build queries.** The YouTube Email Scraper composes `site:youtube.com` queries, e.g. `site:youtube.com tech reviewer "business inquiries" "@gmail.com"`.
3. **Expand queries.** Base queries run first, then quoted, `intitle:` and one variant per query modifier.
4. **Fetch search results.** Pages are retrieved asynchronously with `aiohttp` through the Apify GOOGLE\_SERP proxy.
5. **Parse structurally.** Each result block is isolated around its `<h3>` heading.
6. **Extract emails.** A domain-filtered regex pulls addresses from the block text after normalisation.
7. **Deduplicate and push.** Every new lead is written straight to the dataset as structured data.

Pagination per query is capped by `maxPagesPerQuery`. A query stops early once several consecutive pages produce no new email, so the crawler does not spend proxy calls on an exhausted result set.

Blocked or failed queries are re-queued once at the end of the run. The YouTube Email Scraper then logs a summary: pages fetched, blocked pages, retries and emails per page.

***

### What Data Does It Extract?

Every YouTube Email Scraper dataset item pairs an email with whatever channel metadata Google exposed, plus provenance so you can trace the address back to its query.

Channel results usually expose an `@handle` path, which the YouTube Email Scraper converts into a `username` and a canonical `profileUrl` such as `https://www.youtube.com/@handle`.

Video, playlist and hashtag results are different. Google frequently prints only a video title there, so `username` is `null` and `profileUrl` is empty while `accountName`, the snippet and the email are still returned. That is a Google limitation, not a defect.

***

### Input Schema for the YouTube Email Scraper

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["creator", "founder"]` | Search terms describing the channels you want (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 leading `@` 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 x domain pair in several phrasings |
| `queryModifiers` | array | `["business inquiries", "email", "contact", "sponsorship", "collab"]` | Extra words combined with each keyword when expansion is on |
| `maxPagesPerQuery` | integer 1-50 | `30` | Page cap per query |
| `maxConcurrency` | integer 1-20 | `5` | Parallel queries |

The default modifiers are tuned for YouTube, and `business inquiries` leads the list on purpose. It is the single most common phrase creators put above an address in a channel description, so the YouTube Email Scraper searches it first.

#### JSON input example

```json
{
  "keywords": ["tech reviewer", "home cooking channel", "indie game dev"],
  "location": "",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 600,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["business inquiries", "sponsorship", "collab", "contact"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

***

### Output Schema and Structured Data Fields

Every item the YouTube Email Scraper writes carries all 14 fields below, so a CSV, XLSX or JSON export always has identical columns.

| 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 (channel handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for video results |
| `username` | URL-safe handle when YouTube exposes one; otherwise `null` |
| `profileUrl` | Canonical channel URL when a handle is known; otherwise empty |
| `url` | Direct platform link when exposed, else the profile URL |
| `description` | Channel or video description 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 - verify before sending |
| `foundAt` | ISO 8601 UTC timestamp |

#### JSON output example

```json
[
  {
    "network": "YouTube",
    "keyword": "tech reviewer",
    "query": "site:youtube.com tech reviewer \"business inquiries\" \"@gmail.com\"",
    "title": "Dev Rao Tech - YouTube",
    "accountName": "devraotech",
    "fullName": "Dev Rao Tech",
    "username": "devraotech",
    "profileUrl": "https://www.youtube.com/@devraotech",
    "url": "https://www.youtube.com/@devraotech",
    "description": "Honest laptop and phone reviews every week. Business inquiries: devrao.tech@gmail.com",
    "email": "devrao.tech@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": false,
    "foundAt": "2026-07-09T08:24:16Z"
  },
  {
    "network": "YouTube",
    "keyword": "indie game dev",
    "query": "site:youtube.com indie game dev \"sponsorship\" \"@gmail.com\"",
    "title": "How I shipped my first indie game - YouTube",
    "accountName": "YouTube",
    "fullName": "",
    "username": null,
    "profileUrl": "",
    "url": "https://www.youtube.com/watch?v=8qLm2XcQr4A",
    "description": "Sponsorship enquiries: pixelforge.studio@gmail.com ...",
    "email": "pixelforge.studio@gmail.com",
    "emailDomain": "@gmail.com",
    "possiblyTruncated": true,
    "foundAt": "2026-07-09T08:25:03Z"
  }
]
```

The second row is the honest case. Google served a video page rather than a channel, so there is no handle to build a `profileUrl` from, and the snippet ellipsis touched the address.

***

### How to Use the YouTube Email Scraper in Five Steps

1. **Open the Actor** and confirm your account has Apify proxy access. The GOOGLE\_SERP proxy is required.
2. **Enter 3-10 keywords.** Vertical beats generic: `mechanical keyboard review` outperforms `tech`.
3. **Choose email domains.** Keep `@gmail.com` first - most creators publish a Gmail address - then add `@outlook.com` or a management domain.
4. **Set `maxEmails`.** Start at 20 to check the niche, then raise it.
5. **Run, then export.** Download the dataset as CSV, JSON or XLSX, or pull it via the Apify API into your outreach tool.

Leave `expandQueries` on. Sponsorship-facing phrasing is what separates a channel that wants deals from one that never answers, and the YouTube Email Scraper searches those phrasings for you.

***

### YouTube Email Scraper Use Cases

| Use case | Who it is for | How the YouTube Email Scraper helps |
|---|---|---|
| Sponsorship prospecting | Brands and media buyers | Build a creator list per vertical before pitching integrations |
| Influencer marketing | Agencies | Collect YouTube creator emails at niche scale for campaign shortlists |
| Product seeding | DTC and hardware brands | Reach reviewers who publish a business inquiries address |
| Game key distribution | Game studios and publishers | Find gaming channels advertising sponsorship contacts |
| SaaS review outreach | B2B marketers | Target tutorial and productivity channels in your category |
| Podcast guest booking | Show producers | Source subject-matter creators with a public contact address |
| Affiliate recruiting | Affiliate managers | Assemble a partner pipeline by keyword and country |
| CRM enrichment | RevOps teams | Feed structured data straight into an existing pipeline |

Creators rarely live on one network. Pair this Actor with the [TikTok Email Scraper](https://apify.com/neuro-data/tiktok-email-scraper) and the [Instagram Email Scraper](https://apify.com/neuro-data/instagram-email-scraper) to build a full cross-platform contact set. For long-form writers, the [Substack Email Scraper](https://apify.com/neuro-data/substack-email-scraper) covers the newsletter side.

***

### Why Use This Actor for Creator Contact Discovery

Most YouTube email tools require channel URLs as input, or a logged-in Google account to reveal the About-tab address. The YouTube Email Scraper does neither - it starts from intent and returns whoever Google has already indexed.

Because the YouTube Email Scraper never touches youtube.com, there is no login, no Data API quota and no session to maintain. Its only dependency is Apify's search proxy.

The extraction layer is where the value sits. Normalisation, obfuscation handling, the junk filter, boundary-correct domain matching and soft-wrap repair remove most of the noise naive regex email scraping produces.

Obfuscation matters here more than on most networks. Creators routinely write `name [at] gmail [dot] com` to dodge bots, and the YouTube Email Scraper normalises those forms into a clean address.

***

### Limitations

Read this before planning a campaign around the YouTube Email Scraper.

- **Public index only.** It finds channels whose email is publicly visible in Google's index. Addresses hidden behind YouTube's "View email address" button are not indexed and are out of reach.
- **Google's ~300-result cap.** A single query returns roughly 300 results at most. Query expansion exists to work around that ceiling, so keep `expandQueries` on for volume.
- **`possiblyTruncated`.** When Google's snippet ellipsis touched an address, the row is flagged. Verify those rows before sending.
- **Handle availability.** `username` and `profileUrl` are populated only when Google's result exposes a channel handle. Video, playlist and hashtag results return `accountName` instead.
- **Apify proxy required.** The YouTube Email Scraper cannot run without Apify GOOGLE\_SERP proxy credentials.
- **Free-plan cap.** Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
- **No volume guarantee.** Results vary with keywords, domains, location and what Google has indexed. Nothing is guaranteed, verified or real-time.

The YouTube Email Scraper is not affiliated with, endorsed by or officially supported by YouTube or Google. Use the output in line with GDPR, CAN-SPAM and local marketing law.

***

### Related Actors

The YouTube Email Scraper shares its engine and output schema with every Actor below, all part of the Social, Creator & Community family.

| Actor | What it collects |
|---|---|
| [Facebook Email Scraper](https://apify.com/neuro-data/facebook-email-scraper) | Public contact emails from Facebook pages and profiles |
| [Instagram Email Scraper](https://apify.com/neuro-data/instagram-email-scraper) | Creator and brand emails from Instagram bios in Google's index |
| [TikTok Email Scraper](https://apify.com/neuro-data/tiktok-email-scraper) | Creator collab and booking emails from TikTok results |
| [X Email Scraper](https://apify.com/neuro-data/x-email-scraper) | Founder and freelancer emails from X and Twitter profiles |
| [LinkedIn Email Scraper](https://apify.com/neuro-data/linkedin-email-scraper) | Professional contact emails from public LinkedIn profiles |
| [Pinterest Email Scraper](https://apify.com/neuro-data/pinterest-email-scraper) | Emails from Pinterest creator and brand profiles |
| [Snapchat Email Scraper](https://apify.com/neuro-data/snapchat-email-scraper) | Public emails from Snapchat public profile pages |
| [Reddit Email Scraper](https://apify.com/neuro-data/reddit-email-scraper) | Emails posted publicly in Reddit threads and subreddits |
| [Threads Email Scraper](https://apify.com/neuro-data/threads-email-scraper) | Contact emails from Threads profiles and posts |
| [Tumblr Email Scraper](https://apify.com/neuro-data/tumblr-email-scraper) | Emails from Tumblr blogs and about pages |
| [Telegram Email Scraper](https://apify.com/neuro-data/telegram-email-scraper) | Emails from public Telegram channels and groups |
| [Discord Email Scraper](https://apify.com/neuro-data/discord-email-scraper) | Emails from public Discord server listings |
| [Twitch Email Scraper](https://apify.com/neuro-data/twitch-email-scraper) | Business emails from Twitch streamer pages |
| [Vimeo Email Scraper](https://apify.com/neuro-data/vimeo-email-scraper) | Contact emails from Vimeo creator and studio pages |
| [Dailymotion Email Scraper](https://apify.com/neuro-data/dailymotion-email-scraper) | Emails from Dailymotion channel pages |
| [Likee Email Scraper](https://apify.com/neuro-data/likee-email-scraper) | Emails from Likee short-video creator profiles |
| [Rumble Email Scraper](https://apify.com/neuro-data/rumble-email-scraper) | Emails from Rumble channel pages |
| [Kick Email Scraper](https://apify.com/neuro-data/kick-email-scraper) | Streamer contact emails from Kick profiles |
| [Quora Email Scraper](https://apify.com/neuro-data/quora-email-scraper) | Emails from Quora answers and profile bios |
| [Medium Email Scraper](https://apify.com/neuro-data/medium-email-scraper) | Writer contact emails from Medium profiles and posts |
| [Substack Email Scraper](https://apify.com/neuro-data/substack-email-scraper) | Newsletter author emails from Substack publications |
| [Patreon Email Scraper](https://apify.com/neuro-data/patreon-email-scraper) | Creator contact emails from Patreon pages |
| [Behance Email Scraper](https://apify.com/neuro-data/behance-email-scraper) | Designer emails from Behance portfolios |
| [Dribbble Email Scraper](https://apify.com/neuro-data/dribbble-email-scraper) | Designer and studio emails from Dribbble profiles |
| [DeviantArt Email Scraper](https://apify.com/neuro-data/deviantart-email-scraper) | Artist commission emails from DeviantArt profiles |
| [SoundCloud Email Scraper](https://apify.com/neuro-data/soundcloud-email-scraper) | Artist and label emails from SoundCloud profiles |
| [Mixcloud Email Scraper](https://apify.com/neuro-data/mixcloud-email-scraper) | DJ and podcaster emails from Mixcloud profiles |
| [Goodreads Email Scraper](https://apify.com/neuro-data/goodreads-email-scraper) | Author contact emails from Goodreads profiles |
| [Clubhouse Email Scraper](https://apify.com/neuro-data/clubhouse-email-scraper) | Emails from Clubhouse profile bios |
| [Mastodon Email Scraper](https://apify.com/neuro-data/mastodon-email-scraper) | Emails from Mastodon instance profiles |
| [Bluesky Email Scraper](https://apify.com/neuro-data/bluesky-email-scraper) | Emails from Bluesky profile descriptions |
| [Zhihu Email Scraper](https://apify.com/neuro-data/zhihu-email-scraper) | Emails from Zhihu answers and profiles |
| [VK Email Scraper](https://apify.com/neuro-data/vk-email-scraper) | Emails from VK public pages and profiles |
| [Weibo Email Scraper](https://apify.com/neuro-data/weibo-email-scraper) | Emails from Weibo public profiles and posts |
| [LINE Email Scraper](https://apify.com/neuro-data/line-email-scraper) | Emails from public LINE account pages |
| [KakaoTalk Email Scraper](https://apify.com/neuro-data/kakaotalk-email-scraper) | Emails from public KakaoTalk channel pages |
| [WeChat Email Scraper](https://apify.com/neuro-data/wechat-email-scraper) | Emails from public WeChat account pages |
| [Bigo Live Email Scraper](https://apify.com/neuro-data/bigo-live-email-scraper) | Host contact emails from Bigo Live profiles |
| [Lemon8 Email Scraper](https://apify.com/neuro-data/lemon8-email-scraper) | Creator emails from Lemon8 profiles and posts |
| [Tinder Email Scraper](https://apify.com/neuro-data/tinder-email-scraper) | Public emails indexed from Tinder web pages |
| [Bumble Email Scraper](https://apify.com/neuro-data/bumble-email-scraper) | Public emails indexed from Bumble web pages |
| [Hinge Email Scraper](https://apify.com/neuro-data/hinge-email-scraper) | Public emails indexed from Hinge web pages |

***

### Example: Sourcing Reviewers for a Hardware Launch

Here is a realistic YouTube Email Scraper run. You are launching a mechanical keyboard and want 300 reviewer contacts.

Set `keywords` to `["mechanical keyboard review", "desk setup tour", "keyboard build"]`, `customDomains` to `["@gmail.com"]`, `countryCode` to `US` and `maxEmails` to `300`.

The YouTube Email Scraper builds base, quoted, `intitle:` and modifier variants per keyword - including `sponsorship` and `business inquiries` - then paginates the search results with five parallel workers. Rows stream into the dataset live.

Sort the YouTube Email Scraper dataset by `possiblyTruncated`, verify the flagged rows manually, then load the rest into your sequencer. Re-run the same keywords through the [Twitch Email Scraper](https://apify.com/neuro-data/twitch-email-scraper) to reach the streaming side of the same audience.

***

### YouTube Email Scraper FAQ

**Does the YouTube Email Scraper log into YouTube?**
No. It never authenticates, never opens youtube.com and never uses the YouTube Data API. Every field comes from Google's public search results.

**Where do the YouTube Email Scraper emails actually come from?**
From titles, snippets and site labels Google already publishes for indexed YouTube pages - typically channel and video descriptions where the creator wrote the address themselves.

**Can it reveal the email behind the "View email address" button?**
No. That address is gated and not in Google's index, so the YouTube Email Scraper cannot see it. This Actor only reads what is already public.

**Why do some rows have no `username` or `profileUrl`?**
Because Google's result exposed no channel handle - usually a video, playlist or hashtag page. Those rows still include `accountName`, the email and the snippet.

**What does `possiblyTruncated: true` mean?**
Google's snippet ellipsis touched the address, so it may be cut short. Treat those as leads to verify rather than send-ready contacts.

**How many emails can one YouTube Email Scraper run return?**
Free Apify plans stop at 100 emails per run. Paid plans are uncapped and bounded only by `maxEmails` and what Google has indexed.

**Why does a single query not return thousands of results?**
Google caps one query at roughly 300 results. Query expansion multiplies keyword x domain x phrasing so the YouTube Email Scraper reaches past that ceiling.

**Do I need a proxy to run the YouTube Email Scraper?**
Yes. It requires the Apify GOOGLE\_SERP proxy and will not run without Apify proxy credentials.

**Can I target a country or region?**
Yes. Use `countryCode` for the search proxy's country and `location` for a phrase appended to every query.

**Which query modifiers find the most creator emails?**
`business inquiries` and `sponsorship` are the highest-signal phrases on YouTube. Both ship as defaults.

**Can I resume an interrupted run?**
Yes. Progress is saved in the key-value store, keyed by a hash of your input, and persists on Apify's `PERSIST_STATE`, `MIGRATING` and `ABORTING` events.

**Is scraping YouTube creator emails legal?**
The Actor collects only publicly indexed information, but how you use it is your responsibility. Follow GDPR, CAN-SPAM and local rules on unsolicited outreach.

**How do I get more leads from one niche?**
Add query modifiers, widen `customDomains`, raise `maxPagesPerQuery` and run adjacent sub-niches rather than a single broad category term.

***

### Support

Questions about the YouTube Email Scraper, bug reports or a custom build? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

Search terms describing the YouTube 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 @.

## `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 YouTube.

## `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",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "maxEmails": 20,
  "countryCode": "",
  "expandQueries": true,
  "queryModifiers": [
    "business inquiries",
    "email",
    "contact",
    "sponsorship",
    "collab"
  ],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

# Actor output Schema

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

Records produced by YouTube 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",
        "founder"
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com"
    ],
    "countryCode": "",
    "queryModifiers": [
        "business inquiries",
        "email",
        "contact",
        "sponsorship",
        "collab"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neuro-data/youtube-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",
        "founder",
    ],
    "location": "",
    "customDomains": [
        "@gmail.com",
        "@yahoo.com",
    ],
    "countryCode": "",
    "queryModifiers": [
        "business inquiries",
        "email",
        "contact",
        "sponsorship",
        "collab",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("neuro-data/youtube-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",
    "founder"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "business inquiries",
    "email",
    "contact",
    "sponsorship",
    "collab"
  ]
}' |
apify call neuro-data/youtube-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neuro-data/youtube-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/YRT69bt9limdpym8i/builds/cciI2XD55GiCW9Pbo/openapi.json