# YouTube Channel Email Finder - Creator Emails (`logiover/youtube-creator-email-finder`) Actor

Bulk YouTube creator email extractor: scrape channel contacts without login, then export YouTube email lists to CSV, JSON or Excel for outreach.

- **URL**: https://apify.com/logiover/youtube-creator-email-finder.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Lead generation, Social media, Marketing
- **Features:** Limited permissions
- **Stats:** 419 total users, 21 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 1.00 out of 5 stars

## Pricing

from $3.50 / 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.
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

## YouTube Channel Email Finder — Creator Business Emails in Bulk (No Login, No API Key)

![YouTube Channel Email Finder — Creator Emails](https://img.shields.io/badge/YouTube-Creator%20Email%20Finder-FF0000?logo=youtube\&logoColor=white)

![Apify Actor](https://img.shields.io/badge/Apify-Actor-00A67E?logo=apify\&logoColor=white) ![No login](https://img.shields.io/badge/No%20login-required-2ea44f) ![No API key](https://img.shields.io/badge/No%20API%20key-required-2ea44f) ![Pay per result](https://img.shields.io/badge/Pricing-Pay%20per%20result-1C7ED6) ![Lead Gen](https://img.shields.io/badge/Category-B2B%20Lead%20Gen-8B5CF6) ![Export](https://img.shields.io/badge/Export-JSON%20%7C%20CSV%20%7C%20Excel-F59E0B)

Extract **YouTube creator business emails in bulk** from channel IDs, `@handles` or URLs. This YouTube email scraper reads each creator's business email from the channel About page and — when none is there — crawls the linked website's Contact/About/Impressum pages, turning a channel list into an outreach-ready contact list. **No login, no Google accounts, no CAPTCHA queue.**

> ### 🏆 Why this YouTube email finder?
>
> **Two-layer email extraction** (channel About → linked website) · never guesses — `emailSource` shows `description`, `website` or `none` · boilerplate/platform addresses filtered out (Patreon, Wix, no-reply…) · socials, subscriber count & country for lead qualification · bulk-ready · export to JSON / CSV / Excel. The unofficial **YouTube email API alternative** for influencer outreach and sponsorship prospecting.

***

### ✨ What this Actor does / Key features

- 📧 **Two-layer email extraction** — reads the channel About/description first, then crawls the creator's linked website (Contact/About/Impressum) when no email is published on the channel.
- ✅ **Never a guess** — `emailSource` tells you exactly where each email came from: `description`, `website`, or `none`.
- 🧹 **Boilerplate filtered out** — platform/system addresses (Patreon, Wix, Sentry, no-reply, etc.) are removed so you only get real contact emails.
- 🔗 **Socials & site** — Instagram, TikTok, X/Twitter, Discord, Telegram and more, plus the creator's linked website.
- 📊 **Lead qualification fields** — subscriber count and channel country on every row.
- 🎛️ **Flexible crawling** — toggle linked-site crawling, secondary-email collection and an "only channels with an email" hit-list mode.
- 🔓 **Login-free & safe** — reads only public data (channel About + public websites); no Google account, no login, no CAPTCHA, zero ban risk.
- 📤 **Any format** — export to JSON, CSV, Excel or HTML, or push via the Apify API straight into your CRM or outreach sequence.

### 🚀 Quick start (3 steps)

1. **Configure** — add YouTube channels (`UC…` IDs, `@handles` or full URLs). Channel IDs are the most reliable. Keep **Crawl linked website** on for the best hit rate.
2. **Run** — click **Start**. The Actor resolves each channel, reads the About email, crawls the linked site when needed, and streams contacts into your dataset.
3. **Get your data** — open the **Output** tab and export to **JSON, CSV, Excel or HTML**, or pull it via the Apify API.

### 📥 Input

Give the Actor at least one value in `channels`. Everything else is optional.

#### Example — clean hit-list of channels with an email

```json
{
  "channels": ["@mkbhd", "@MrBeast", "UCBJycsmduvYEL83R_U4JriQ"],
  "crawlLinkedSite": true,
  "onlyWithEmail": true
}
```

#### Example — deep crawl for maximum coverage

```json
{
  "channels": ["@LinusTechTips", "@veritasium", "@Mrwhosetheboss"],
  "crawlLinkedSite": true,
  "alwaysCrawlSite": true,
  "maxSitePages": 5
}
```

#### Example — description-only, fast pass

```json
{
  "channels": ["UCBJycsmduvYEL83R_U4JriQ", "UCXuqSBlHAE6Xw-yeJA0Tunw"],
  "crawlLinkedSite": false,
  "maxResults": 200
}
```

| Field | Type | Default | Description |
|---|---|---|---|
| `channels` *(required)* | array | — | Channel IDs (`UC…`), `@handles`, or URLs. |
| `crawlLinkedSite` | boolean | `true` | Crawl the linked site when no email is in the description. |
| `alwaysCrawlSite` | boolean | `false` | Crawl the site even if an email was already found (collects secondary emails). |
| `maxSitePages` | integer | `3` | Pages of the linked site to scan (homepage + contact/about). |
| `onlyWithEmail` | boolean | `false` | Skip channels with no email found. |
| `maxResults` | integer | `0` | Stop after N channels. `0` = no limit. |

> **Where do I get channel lists?** Build a niche channel list with a YouTube search/discovery scraper, then feed those channels straight into this Actor. Creators who already run sponsorships, brand deals or a business/website almost always list a business email.

### 📤 Output

One row per channel — exportable to JSON, CSV, Excel or HTML. Here is a trimmed sample record:

```json
{
  "channelTitle": "Marques Brownlee",
  "handle": "@mkbhd",
  "channelUrl": "https://www.youtube.com/@mkbhd",
  "subscriberCount": 19800000,
  "email": "business@mkbhd.com",
  "emails": ["business@mkbhd.com"],
  "emailSource": "description",
  "linkedWebsite": "http://shop.MKBHD.com/",
  "socialLinks": ["https://www.instagram.com/mkbhd", "https://x.com/MKBHD"],
  "country": "US"
}
```

<details>
<summary><b>📋 Full field reference (click to expand)</b></summary>

| Field | Description |
|-------|-------------|
| `channelTitle` | the creator / channel name |
| `handle` | the channel `@handle` |
| `channelUrl` | the channel URL |
| `email` | the primary business email found |
| `emails` | all emails found (de-duplicated) |
| `emailSource` | where the email came from: `description`, `website`, or `none` (never a guess) |
| `linkedWebsite` | the creator's linked site |
| `socialLinks` | Instagram, TikTok, X/Twitter, Discord, Telegram and more |
| `subscriberCount` | for quick lead qualification |
| `country` | channel country |

</details>

#### Additional output fields

These fields are also present in the dataset:

| Field | Type | Description |
|---|---|---|
| `query` | — | The channel input as provided (ID, @handle or URL). |
| `channelId` | — | Resolved YouTube channel ID (UC...). |
| `subscriberCountText` | — | Subscriber count as shown on YouTube. |
| `siteCrawled` | — | Website that was crawled for emails, if any. |
| `avatar` | — | Channel avatar image URL. |
| `scrapedAt` | — | ISO timestamp when the channel was processed. |

### 💡 Use cases

- **Influencer outreach** — find creator emails to pitch collaborations and product seeding.
- **Sponsorship prospecting** — build targeted YouTube influencer email lists for brand deals.
- **Agency lead generation** — extract YouTube emails in bulk for client prospect lists.
- **Media buying & PR outreach** — get channel contact emails for placements and press.
- **Affiliate & UGC recruiting** — find creators to onboard into your program.
- **CRM enrichment** — append emails, socials and subscriber counts to a channel list you already have.

### 👥 Who uses it

Influencer-marketing & talent teams · brand & sponsorship managers · lead-gen & outreach agencies · PR & media-buying teams · affiliate & UGC program managers · growth teams building creator contact lists.

### 💰 Pricing

This Actor runs on a simple **pay-per-result** model — you pay for the channel rows you extract, with no separate Apify platform fees to calculate. Try it on the **free tier** first, then scale up. See the **Pricing** tab on this page for the current rate.

### ❓ Frequently Asked Questions

**Does it get the email behind YouTube's "View email address" button?**
No — that email is gated behind a logged-in Google account and a CAPTCHA. This Actor harvests the emails creators publish openly in their **description** and on their **linked website**, with zero accounts and zero ban risk — which is exactly where a large share of monetizing creators put their business contact.

**What's the hit rate?**
It depends on your input list — channels that actively monetize almost always publish a contact email. The `emailSource` field shows whether each email came from the description or the website, and `none` when a creator hasn't published one.

**Do I get charged when no email is found?**
You still get a row with `emailSource: "none"` so you can see coverage. Enable `onlyWithEmail` to keep just the hits.

**What input formats are supported?**
Channel IDs (`UC…`), `@handles`, and full channel URLs (`/channel/...`, `/@...`, `/c/...`).

#### How do I scrape YouTube emails without login?

This Actor reads only public data — the channel About description and the creator's linked website — so it needs no Google account, no login and no CAPTCHA. You feed in channels and get back published contact emails.

#### How do I export YouTube channel data to CSV or JSON?

Every run is a dataset you can download as CSV, JSON, Excel or HTML, or pull via the Apify API. Each row holds the channel, email, linked website, socials and subscriber count — ready for outreach.

#### Is this a YouTube email API alternative?

Yes. Instead of YouTube's gated "View email address" button or the official Data API, it harvests the business emails creators publish openly, then hands you a clean bulk export of YouTube creator contacts.

#### How do I export only YouTube channels that have an email?

Enable `onlyWithEmail` to drop channels with no address found, leaving a clean, outreach-ready hit list of creator emails you can export to CSV or Excel.

### 🔗 More lead-gen & contact scrapers by logiover

Building a full creator/B2B outreach pipeline? Pair the email finder with the rest of the lead-gen suite:

| Actor | What it does |
|---|---|
| [Website Contact Scraper](https://apify.com/logiover/website-contact-scraper) | Emails, phones & socials from any website |
| [Bulk Email Verifier](https://apify.com/logiover/bulk-email-deliverability-checker) | Validate extracted emails before you send |
| [Bulk Email Deliverability Checker](https://apify.com/logiover/bulk-email-deliverability-checker) | Check inbox-deliverability of a list |
| [TikTok Profile & Email Scraper](https://apify.com/logiover/tiktok-profile-email-scraper) | Creator emails & profiles from TikTok |
| [Bulk Social Profile Extractor](https://apify.com/logiover/bulk-social-profile-extractor) | Find social profiles for a list of names/domains |
| [B2B Lead Scraper](https://apify.com/logiover/b2b-lead-scraper) | Sector + country company & person leads |
| [Leads Scraper](https://apify.com/logiover/b2b-lead-scraper) | OSM-based B2B lead generation |
| [Bulk WHOIS/RDAP Lookup](https://apify.com/logiover/bulk-whois-rdap-lookup) | Domain owner & registration data |
| [Subdomain Finder](https://apify.com/logiover/subdomain-finder) | Enumerate a domain's subdomains |

👉 Browse all **[logiover scrapers on Apify Store](https://apify.com/logiover)** — 180+ actors across real estate, jobs, crypto, social media & B2B data.

### ⏰ Scheduling & integration

Schedule this Actor on Apify to refresh your creator contact lists on any cadence. Export results to JSON, CSV or Excel, sync to Google Sheets, or push straight into your CRM, outreach tool and webhooks through the Apify API. Chain it with a discovery scraper (build the list) and a verifier (validate the emails) for an end-to-end outreach pipeline via **Make, n8n or Zapier**.

### 🤖 AI Agents, MCP & RAG Integration

**YouTube Channel Email Finder** works natively as an on-demand data tool for AI assistants and autonomous workflows.

Connect this Actor directly to **Apify AI**, **Claude Desktop**, **Cursor**, **VS Code**, **Windsurf**, **LangChain**, or **LlamaIndex** via the official **Apify MCP Server** — no custom wrapper code needed:

```json
{
  "mcpServers": {
    "apify": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=logiover/youtube-creator-email-finder"
    }
  }
}
```

- **Schema-typed inputs & outputs:** Clean JSON records with explicit `.actor/input_schema.json` and `.actor/output_schema.json` definitions so LLM agents infer parameters and parse fields accurately without HTML noise.
- **Bounded & predictable runs:** Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
- **RAG & automation ready:** Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.

### 💬 Support, Issues & Reviews

- **Bug reports & target-site changes:** Hit an unexpected empty result or selector change? [Open a ticket in the Issues tab](https://apify.com/logiover/youtube-creator-email-finder/issues) with your **Run ID** or sample input — we actively monitor issues and ship fixes fast.
- **Feature & field requests:** Need an additional data attribute or filter? [Request it in the Issues tab](https://apify.com/logiover/youtube-creator-email-finder/issues).
- **Enjoying this Actor?** If it saved you engineering time, please consider leaving an honest [review on Apify Store](https://apify.com/logiover/youtube-creator-email-finder/reviews) or bookmarking [logiover/youtube-creator-email-finder](https://apify.com/logiover/youtube-creator-email-finder) — organic developer feedback helps others discover reliable tools and keeps maintenance prioritized.

### ⚖️ Legal

This Actor reads only publicly available data — channel descriptions and public websites — and never logs into any account or bypasses a login wall. You are responsible for using the data in line with YouTube's Terms and applicable privacy laws (GDPR/CCPA). Not affiliated with YouTube / Google.

***

**Keywords:** youtube email scraper, youtube channel email finder, youtube creator email extractor, youtube influencer email list, scrape youtube emails without login, youtube email api alternative, youtube creator contact export csv, influencer outreach lead generation, youtube channel data export.

***

### How much YouTube Channel data can you extract in one run?

This Actor returns **one row per item you supply**, so the volume is yours to set: give it ten rows and you get ten rows, give it a thousand and you get a thousand. The run measured below handled 2 in 19 seconds. That is roughly **6 rows a minute**.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much YouTube Channel itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

### YouTube Channel scraping — frequently asked questions

#### Do I need a YouTube Channel API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

#### How do I export YouTube Channel data to CSV, Excel, JSON or Google Sheets?

Open the **Storage** tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

#### Can I schedule this YouTube Channel scraper to run daily or hourly?

Yes. Use the **Schedules** tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the rows you care about really do change that fast.

#### How many rows can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

#### Is scraping YouTube Channel legal?

This Actor collects only information that YouTube Channel publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

#### What happens if YouTube Channel blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run **fails with the reason** instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

#### Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

### 📝 Changelog

#### 2026-11-14

- Verified live production health run (2026-11-14): extracted **2** structured records in **7.7s** with valid schema output.
- Hardened internal proxy stall fallback and pay-per-event dataset instance budget protection.

#### 2026-11-11

- Added reliable terminal run status telemetry and structured Apify AI / MCP Server (`mcp.apify.com`) tool configuration.
- Added direct Issues & Reviews support links and refreshed live maintenance verification.

#### 2026-11-01

- Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
- README refreshed: 2 links to renamed Actors updated, 2 links to retired Actors removed; documented 6 additional output fields.

#### 2026-10-15

- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.

#### 2026-09-23

- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Output verified on a live run: 18 columns returned, 86.1% of cells populated.
- Run reliability reviewed: 99.5% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
- Noted that 1 column(s) came back empty in this sample (`country`); these are under review.

#### 2026-09-01

- Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
- Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
- No change to input, output fields or scraping logic.

#### 2026-08-11

- Maintenance release: refreshed the build and dependencies.
- Re-verified live execution, non-empty structured output and dataset field/type integrity.
- Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

#### 2026-08-01

- Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
- Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
- Fixed the run Output link from `{{links.apiDefaultDatasetUrl}}` to `{{links.apiDefaultDatasetUrl}}/items` so the results table opens the dataset items endpoint.

#### 2026-08-01 — Health-check remediation

- August 2026 monthly health-check remediation is in progress; this build contains fixes verified from empty/default, Console-default, targeted live probes, or field-level semantic review.
- Fixed the run Output link from `{{links.apiDefaultDatasetUrl}}` to `{{links.apiDefaultDatasetUrl}}/items` so the results table opens the dataset items endpoint.
- The final four-input matrix verdict will be appended after post-build cloud revalidation.

#### 2026-07-06

- ✨ README overhaul: shields badge row, green highlight callout, collapsible full field reference, extra ready-to-run examples, lead-gen suite cross-links and clearer quick-start.

#### 2026-07-01

- Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
- Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
- Added ready-to-run example tasks that cover common real-world use cases.

#### 2026-06-15

- Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

#### 2026-06-07

- Docs: added coverage for scraping YouTube emails without login, exporting YouTube channel data to CSV/JSON, and using the actor as a YouTube email API alternative.

#### 2026-06-05

- 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
- ⚡ Stability & performance hardening; fresh rebuild.

#### 2026-06-04

- Verified live & refreshed build — reliability/maintenance pass.

***

\*Maintained: last verified 2026-11-14 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).

# Changelog

This Actor's version history is a separate document: https://apify.com/logiover/youtube-creator-email-finder/changelog.md

# Actor input Schema

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

Channel IDs (UC...), @handles, or full channel URLs. Channel IDs are the most reliable. Leave empty to run on a default set of popular creators.

## `crawlLinkedSite` (type: `boolean`):

When no email is found in the channel description, follow the creator's linked website and scan its Contact/About pages. Boosts hit rate significantly.

## `alwaysCrawlSite` (type: `boolean`):

Crawl the linked website even when an email was already found in the description (collects additional/secondary emails).

## `maxSitePages` (type: `integer`):

How many pages of the linked site to scan (homepage + contact/about variants).

## `onlyWithEmail` (type: `boolean`):

Skip channels where no email was found. Keep off to see full coverage and email source.

## `maxResults` (type: `integer`):

Stop after this many channels (0 = no limit). Keeps the run fast and cheap.

## Actor input object example

```json
{
  "channels": [
    "@veritasium",
    "UCBJycsmduvYEL83R_U4JriQ"
  ],
  "crawlLinkedSite": true,
  "alwaysCrawlSite": false,
  "maxSitePages": 3,
  "onlyWithEmail": false,
  "maxResults": 100
}
```

# Actor output Schema

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

Dataset of YouTube channels with extracted business emails, linked websites and social links.

# 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",
        "@mkbhd",
        "UCBJycsmduvYEL83R_U4JriQ"
    ],
    "maxSitePages": 3
};

// Run the Actor and wait for it to finish
const run = await client.actor("logiover/youtube-creator-email-finder").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",
        "@mkbhd",
        "UCBJycsmduvYEL83R_U4JriQ",
    ],
    "maxSitePages": 3,
}

# Run the Actor and wait for it to finish
run = client.actor("logiover/youtube-creator-email-finder").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",
    "@mkbhd",
    "UCBJycsmduvYEL83R_U4JriQ"
  ],
  "maxSitePages": 3
}' |
apify call logiover/youtube-creator-email-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,logiover/youtube-creator-email-finder"
        }
    }
}
```

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/eiYd1tL0iFmEhMT4o/builds/QK9FReHQ7NlL58UGR/openapi.json
