# YouTube Channel Email Scraper (`adaptable_wheelhouse/youtube-channel-email-scraper`) Actor

Get YouTube channel emails from the description, About text and linked websites, and from the View email address button when you supply a Google session and a CAPTCHA key.

- **URL**: https://apify.com/adaptable_wheelhouse/youtube-channel-email-scraper.md
- **Developed by:** [Mr T](https://apify.com/adaptable_wheelhouse) (community)
- **Categories:** Social media, Videos
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 emails

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?

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

### YouTube Channel Email Scraper

Collects email addresses for YouTube channels from two places:

1. **Text the creator published.** The channel description, the About panel, video blurbs embedded on the channel page, and the websites linked from About (social profiles are skipped).
2. **The "View email address" button.** YouTube only returns this after a signed-in Google session, and it usually asks for a CAPTCHA. Pass your own session cookie and a 2Captcha or CapSolver key and the actor opens the button. You pay the CAPTCHA provider yourself.

**You pay per email returned.** A channel with no address, and a channel that does not exist, still appears in the results so you can see what happened, and those rows are free.

#### Example input

Public emails only:

```json
{
    "channels": ["@MrBeast", "https://www.youtube.com/@mkbhd", "UCX6OQ3DkcsbYNE6H8uQQuVA"],
    "maxWebsiteLinks": 5
}
```

Also open the business-email button:

```json
{
    "channels": ["@SomeCreator"],
    "googleCookie": "SID=...; HSID=...; SSID=...; APISID=...; SAPISID=...",
    "captchaProvider": "2captcha",
    "captchaApiKey": "YOUR_KEY"
}
```

The cookie has to be the `cookie` request header from a signed-in `youtube.com` request (Chrome DevTools → Network). `document.cookie` does not include the login cookies, because they are HTTP-only.

#### Example output

```json
{
    "input": "@MrBeast",
    "channelId": "UCX6OQ3DkcsbYNE6H8uQQuVA",
    "channelName": "MrBeast",
    "channelUsername": "@mrbeast",
    "channelUrl": "https://www.youtube.com/channel/UCX6OQ3DkcsbYNE6H8uQQuVA",
    "email": "chucky@mrbeastbusiness.com",
    "source": "channel_page",
    "numberOfSubscribers": 523000000,
    "channelLocation": "US",
    "channelTotalViews": 144353642443,
    "businessEmailListed": true
}
```

`source` is `business_button` for the signed-in reveal, and `about`, `description`, `link`, `channel_page` or `website` for text the creator published. One channel can produce several rows. The same address is returned once, from the strongest source.

When nothing is found:

```json
{
    "url": "@unknown",
    "input": "@unknown",
    "error": "NO_EMAIL",
    "note": "No email found in the channel text, its links, or the business-email button"
}
```

| `error` | Meaning |
|---|---|
| `NO_EMAIL` | Nothing published, and the button did not return one. |
| `CHANNEL_DOES_NOT_EXIST` | No channel at that URL. |
| `NOT_SIGNED_IN` | The cookie is missing or expired, and no public email was found. |
| `CAPTCHA_REQUIRED` | YouTube asked for a CAPTCHA and no key was set. |
| `CAPTCHA_FAILED` | 2Captcha or CapSolver could not solve it. |
| `CAPTCHA_REJECTED` | YouTube rejected the solved token. Public emails are still returned when any were found. |
| `INVALID_INPUT` | Not a channel URL, handle or ID. |

YouTube sometimes rejects a CAPTCHA token that was not solved inside a real browser session. When that happens the public emails are still saved and the run log says `CAPTCHA_REJECTED`.

#### Proxies

The default proxy is Apify Residential. The CAPTCHA solve, when you use one, is sent through the same proxy IP as the YouTube request.

#### Is it legal?

This actor reads public channel pages, and the business-email button only with a session you provide. Those addresses are personal data under laws such as GDPR. Use them only where you have a legitimate reason, and check with a lawyer if you are unsure.

# Actor input Schema

## `channels` (type: `array`):

YouTube channels to check. Accepts @handle, a UC… channel ID, and /@handle, /channel/UC…, /c/name and /user/name URLs.

## `maxWebsiteLinks` (type: `integer`):

How many of each channel's own links (About links that are not social profiles) to open looking for an email. 0 skips websites.

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

How many channels to check at the same time.

## `googleCookie` (type: `string`):

Optional. The Cookie header from a signed-in youtube.com request (Chrome DevTools → Network → any youtubei request → Request Headers → cookie). Needed for the View email address button. document.cookie is not enough, because the login cookies are HTTP-only.

## `captchaProvider` (type: `string`):

Used only when YouTube asks for a CAPTCHA while opening the business email. You pay the provider directly.

## `captchaApiKey` (type: `string`):

Your 2Captcha or CapSolver key. The solve is sent from the same proxy IP as the YouTube request.

## `proxyConfiguration` (type: `object`):

YouTube blocks most datacenter IPs. Residential proxies are recommended.

## Actor input object example

```json
{
  "channels": [
    "@MrBeast"
  ],
  "maxWebsiteLinks": 5,
  "maxConcurrency": 3,
  "captchaProvider": "2captcha",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `emails` (type: `string`):

One row per email found. Channels with no email, and channels that could not be opened, are separate uncharged rows.

# 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 = {
    "channels": [
        "@MrBeast"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("adaptable_wheelhouse/youtube-channel-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 = {
    "channels": ["@MrBeast"],
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("adaptable_wheelhouse/youtube-channel-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 '{
  "channels": [
    "@MrBeast"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call adaptable_wheelhouse/youtube-channel-email-scraper --silent --output-dataset

```

## MCP server setup

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