# Twitch Email Scraper (`leads-scraper/twitch-email-scraper`) Actor

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

- **URL**: https://apify.com/leads-scraper/twitch-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

### Twitch Email Scraper — find public streamer contact emails at scale

The **Twitch Email Scraper** is an Apify Actor that collects publicly indexed contact emails belonging to Twitch channels, streamers and gaming creators. It turns a list of keywords into a clean, structured dataset of leads.

Streamers put "business inquiries: name@gmail.com" in their About panel, and Google indexes that text. The Twitch Email Scraper searches Google for exactly those pages and pulls the addresses out.

This is a *search-based* twitch email extractor. It never logs into Twitch, never uses the Twitch API, and never opens twitch.tv. Every field comes from publicly available Google search results.

If you have ever tried a manual twitch streamer email finder workflow — searching `site:twitch.tv "gmail.com" valorant`, copying addresses into a spreadsheet — this Actor is that workflow, automated, deduplicated and exported as JSON or CSV.

#### Who it is for

- Brand and agency teams running twitch sponsorship outreach
- Influencer marketing managers building gaming creator lists
- Esports orgs scouting talent and casters
- SaaS and peripheral brands doing twitch lead generation
- Recruiters hiring editors, mods and channel managers

***

### Key features

The Twitch Email Scraper ships with the parsing, deduplication and reliability behaviour below. Everything listed here is implemented in the Actor — nothing is aspirational.

| Feature | What it does |
|---|---|
| Google `site:` search | Builds queries against `twitch.tv` so only Twitch pages are parsed |
| Query expansion | Base, quoted and `intitle:` variants plus one query per modifier |
| Query modifiers | Defaults tuned for Twitch: `business inquiries`, `email`, `contact`, `sponsorship`, `collab` |
| Domain filtering | Keeps only emails on the domains you list, e.g. `@gmail.com` |
| Global deduplication | One row per unique email across every query and every page |
| Email normalisation | Understands `name [at] domain [dot] com`, `(at)`, `name @ domain.com`, `＠` and zero-width characters |
| Junk filter | Rejects placeholders like `email@`, `yourname@`, `test@`, `xxx@` |
| Boundary-correct matching | `@gmail.com` will not match inside `@gmail.company` or `@gmail.com.br` |
| Concurrency | An `asyncio` worker pool runs several queries in parallel |
| Retry logic | Up to 3 attempts per page with exponential backoff and a fresh proxy session |
| Block detection | CAPTCHA, "unusual traffic" and consent pages are detected and retried, not counted as empty |
| Resumable state | Run state is stored in the key-value store and survives migration |
| Fallback parser | If Google's markup changes, extraction degrades to emails-without-details, not zero results |
| Streaming dataset | Each lead is pushed to the Apify dataset the moment it is found |

***

### How the Twitch Email Scraper works

The Twitch Email Scraper is a Google SERP crawler with an email parser bolted onto it. There is no browser, no JavaScript rendering, no authentication and no cookies.

**1. Read the input.** Keywords, location, email domains and limits are loaded from the Actor input.

**2. Build the queries.** Each keyword is combined with each email domain and the `site:twitch.tv` operator, for example:

```
site:twitch.tv streamer "@gmail.com" "Los Angeles"
```

**3. Expand the query set.** With `expandQueries` on, every keyword × domain pair also runs as a quoted phrase, an `intitle:` query, and one variant per modifier. Base queries run first, so the highest-signal search results arrive early.

**4. Fetch through the proxy.** Result pages are requested asynchronously with `aiohttp` through the Apify **GOOGLE\_SERP** proxy, with pagination up to `maxPagesPerQuery`.

**5. Parse structurally.** For each result the parser locates the `<h3>` title, then walks up to the smallest surrounding block. It does **not** depend on Google's CSS class names, which change often.

**6. Extract and clean.** A domain-filtered regex pulls emails from the block text. Soft-wrap repair drops a hit that is only the tail of another email in the same block.

**7. Deduplicate and push.** Emails are deduplicated globally, then written straight to the dataset. The run stops as soon as `maxEmails` unique addresses exist.

Failed or blocked queries are re-queued once at the end of the run, so a temporary block does not silently cost you leads.

***

### What data does the Twitch Email Scraper extract?

Every dataset item produced by the Twitch Email Scraper contains the same 14 fields. Nothing is optional and nothing is nested, so the output schema maps cleanly onto a CRM import or a Google Sheet.

You get the email itself, the domain it matched, the account metadata Google printed, the exact query that produced the lead, and a truncation flag.

The `description` field holds the bio or panel snippet Google displayed, cleaned of labels and engagement counters — useful for qualifying a streamer before you write the first line of an outreach email.

Because the Twitch Email Scraper stores the originating `keyword` and `query` on every row, you can measure which searches actually produced leads and drop the ones that did not.

***

### Input fields

The Twitch Email Scraper input schema is deliberately small. These nine fields are the entire configuration surface of the Twitch Email Scraper.

| Field | Type | Default | Meaning |
|---|---|---|---|
| `keywords` | array (required) | `["streamer", "creator"]` | Search terms: niche, game, role or 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 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` | Pagination cap per query |
| `maxConcurrency` | integer 1–20 | `5` | Parallel queries |

Keyword choice matters more than any other setting. `just chatting streamer` and `speedrunner` return very different lead pools.

***

### Output fields and dataset structure

The output schema of the Twitch Email Scraper is fixed. Every row the Twitch Email Scraper writes carries all 14 fields below, so downstream parsing never has to guess.

| 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 (handle or display name) |
| `fullName` | Display name parsed from a profile-style title; empty for clip or VOD titles |
| `username` | URL-safe handle when Twitch exposes one; otherwise `null` |
| `profileUrl` | Canonical channel URL when a handle is known; otherwise empty |
| `url` | Direct Twitch link when exposed, else the profile URL |
| `description` | Bio or panel 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 |

Export the dataset as JSON, CSV, Excel or XML from the Apify console, or pull it through the API.

***

### How to use the Twitch Email Scraper

Running the Twitch Email Scraper takes about a minute of setup.

1. Open the **Twitch Email Scraper** on Apify and click **Try for free**.
2. Replace the default keywords with your niche — `speedrunner`, `variety streamer`, `esports coach`.
3. Set `customDomains` to the mailbox providers you care about. `@gmail.com` alone is the highest-yield single choice for creators.
4. Optionally set `location` and `countryCode` to bias results geographically.
5. Raise `maxEmails` to the volume you need, then **Start**.
6. Watch the log — it reports pages fetched, blocked pages, retries and emails per page.
7. Export the dataset, or schedule the Actor to re-run weekly and append fresh leads.

**Tip:** run two or three narrow keyword sets rather than one broad one. Google caps a single query at roughly 300 results, so five focused queries beat one generic query every time.

***

### Use cases and lead generation workflows

Teams use the Twitch Email Scraper wherever contact discovery on the gaming side of the creator economy is the bottleneck. The Twitch Email Scraper fits equally well as a one-off list build or a scheduled data collection job.

| Use case | How the Twitch Email Scraper helps |
|---|---|
| Sponsorship outreach | Build a list of streamers in a game category who publish a business email |
| Influencer marketing | Source micro-streamers by niche and location for campaign shortlists |
| Esports recruiting | Find casters, analysts and coaches advertising contact details |
| Peripheral and energy-drink brands | Contact discovery across gaming creators for product seeding |
| Agency prospecting | Assemble a talent roster of unsigned creators to pitch representation |
| Editor and thumbnail services | Reach streamers who list a contact address for freelance work |
| Market research | Collect structured data on how creators in a niche describe themselves |
| CRM enrichment | Match handles and channel URLs to existing records |

***

### Why choose this Actor

**It is honest about its source.** Everything comes from Google's public index. No login, no scraping behind a wall, no fake "verified" badge on the data.

**It survives Google layout changes.** Structural parsing plus a whole-page fallback means a markup change degrades quality rather than breaking the run.

**It is built for volume without waste.** Global deduplication, a shared stop signal on `maxEmails`, and streaming dataset writes mean the Twitch Email Scraper collects the leads you asked for and then stops.

**It is one input schema across 40+ platforms.** Learn the Twitch Email Scraper once and every sibling Actor behaves identically.

If you also work other creator platforms, pair this with the [YouTube Email Scraper](https://apify.com/leads-scraper/youtube-email-scraper) for long-form channels, the [Kick Email Scraper](https://apify.com/leads-scraper/kick-email-scraper) for streamers who moved off Twitch, and the [Discord Email Scraper](https://apify.com/leads-scraper/discord-email-scraper) for the community servers those same streamers run.

***

### Limitations

Read this before you run the Twitch Email Scraper. These are real constraints of the Twitch Email Scraper, not boilerplate disclaimers.

- **Public index only.** Only accounts whose email is visible in Google's index can be found. A streamer who hides their address will not appear.
- **~300 results per query.** Google caps a single query at roughly 300 results. That is exactly why `expandQueries` exists — leave it on.
- **Truncated emails.** `possiblyTruncated: true` means Google's snippet ellipsis touched the address. Verify those rows before sending.
- **Handle availability.** `username` and `profileUrl` are only populated when Twitch's handle appears in the result. Where Google shows only a display name, you still get `accountName` and `fullName` but an empty handle. This is a Google limitation, not a bug.
- **Proxy requirement.** The Actor requires the Apify **GOOGLE\_SERP** proxy and cannot run without Apify proxy credentials.
- **Free-plan cap.** Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.
- **No volume guarantee.** Results from the Twitch Email Scraper vary with keywords, domains and location.

Use the output responsibly and in line with GDPR, CAN-SPAM and your local rules on unsolicited email.

***

### Related Actors

The Twitch Email Scraper is one of a family of Actors that share the same crawler, parser and output schema. Swap the platform, keep the workflow.

| Actor | What it collects |
|---|---|
| [Twitch Email and Phone Number Scraper](https://apify.com/leads-scraper/twitch-email-and-phone-number-scraper) | Emails and phone numbers from Twitch |
| [Twitch Phone Number Scraper](https://apify.com/leads-scraper/twitch-phone-number-scraper) | Public phone numbers from Twitch |
| [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 |
| [Rumble Email Scraper](https://apify.com/leads-scraper/rumble-email-scraper) | Public contact emails from Rumble |
| [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 |
| [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 |

### Example: JSON input and dataset output

Here is a realistic Twitch Email Scraper input targeting variety streamers in the United States:

```json
{
  "keywords": ["variety streamer", "esports coach"],
  "location": "United States",
  "customDomains": ["@gmail.com", "@outlook.com"],
  "maxEmails": 250,
  "countryCode": "US",
  "expandQueries": true,
  "queryModifiers": ["business inquiries", "email", "contact", "sponsorship", "collab"],
  "maxPagesPerQuery": 30,
  "maxConcurrency": 5
}
```

And a single dataset item the Twitch Email Scraper returns:

```json
{
  "network": "Twitch",
  "keyword": "variety streamer",
  "query": "site:twitch.tv variety streamer \"@gmail.com\" \"United States\" business inquiries",
  "title": "pixelnovaplays - Twitch",
  "accountName": "pixelnovaplays",
  "fullName": "Nova Reyes",
  "username": "pixelnovaplays",
  "profileUrl": "https://www.twitch.tv/pixelnovaplays",
  "url": "https://www.twitch.tv/pixelnovaplays",
  "description": "Variety streamer, cozy games and shooters. Business inquiries: nova.reyes.tv@gmail.com",
  "email": "nova.reyes.tv@gmail.com",
  "emailDomain": "@gmail.com",
  "possiblyTruncated": false,
  "foundAt": "2026-08-31T09:14:22Z"
}
```

***

### FAQ about the Twitch Email Scraper

#### Does the Twitch Email Scraper log into Twitch?

No. The Twitch Email Scraper never logs in, never uses the Twitch API and never opens twitch.tv. All data comes from publicly indexed Google search results.

#### Where do the emails come from?

From the titles, snippets and site labels Google prints for Twitch pages — typically the About panel where streamers publish business inquiry addresses.

#### Can the Twitch Email Scraper find private or hidden emails?

No. If an address is not in Google's public index, this twitch email extractor cannot find it.

#### How is this different from a Twitch API tool?

The Twitch Email Scraper works entirely from search results, so it needs no API key, no OAuth token and no channel permissions.

#### Why do some rows have an empty `username` and `profileUrl`?

Because Google showed only a display name for that result. You still get `accountName`, `fullName` and the email. It is a Google limitation, not a bug.

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

Google's snippet ellipsis touched the email, so it may be cut off. Verify those addresses before sending.

#### Do I need a proxy to run the Twitch Email Scraper?

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

#### How many emails can I get on a free plan?

Free Apify plans are capped at 100 emails per run. Paid plans are uncapped.

#### Should I leave `expandQueries` on?

Yes, in almost every case. Google caps one query at roughly 300 results, and the Twitch Email Scraper spreads your search across base, quoted, `intitle:` and modifier variants to work around that cap.

#### How do I get more results from a twitch streamer email finder run?

Use more specific keywords, add more email domains, raise `maxPagesPerQuery`, and run separate jobs per game category or region.

#### Can I schedule the Twitch Email Scraper?

Yes. Schedule it on Apify and it will append new leads to the dataset on each run. Run state is resumable and survives platform migrations.

#### Is the output ready for a CRM?

Yes. The Twitch Email Scraper produces flat structured data with 14 fixed fields, exportable as JSON, CSV, Excel or XML.

#### Does it deduplicate across runs?

Deduplication is global within a run. Across scheduled runs, deduplicate on the `email` field in your CRM or warehouse.

#### Is this affiliated with Twitch?

No. The Twitch Email Scraper is independent and is not affiliated with, endorsed by or officially supported by Twitch.

***

### Leave a review

If the Twitch 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, a bug, or need a custom build of the Twitch Email Scraper for a different platform or field set? Email **neurodata.apify@gmail.com**.

# Actor input Schema

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

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

## `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": [
    "streamer",
    "creator"
  ],
  "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 Twitch 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": [
        "streamer",
        "creator"
    ],
    "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("leads-scraper/twitch-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": [
        "streamer",
        "creator",
    ],
    "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("leads-scraper/twitch-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": [
    "streamer",
    "creator"
  ],
  "location": "",
  "customDomains": [
    "@gmail.com",
    "@yahoo.com"
  ],
  "countryCode": "",
  "queryModifiers": [
    "business inquiries",
    "email",
    "contact",
    "sponsorship",
    "collab"
  ]
}' |
apify call leads-scraper/twitch-email-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leads-scraper/twitch-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/mHnO1jhfvcmAQxRFJ/builds/rc3WRkFaSy4MSYXGS/openapi.json