# Twitch Email Finder (`zucchini_gopher_m2v/twitch-email-scraper`) Actor

Extract publicly-published business contact emails from Twitch streamers' channel bio and About panels -- no account or API key needed.

- **URL**: https://apify.com/zucchini\_gopher\_m2v/twitch-email-scraper.md
- **Developed by:** [Faisal Ahdan naufal](https://apify.com/zucchini_gopher_m2v) (community)
- **Categories:** Automation, Developer tools, Lead generation
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## 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?

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

## Twitch Email Finder

Extract publicly-published business contact emails from Twitch streamers' channel bio and About panels — no account or API key needed.

### Why use this actor

- Finds real contact emails streamers have already chosen to publish for sponsorship/business inquiries — nothing private, nothing guessed
- Checks **both** the channel bio and every About panel — a real test run found a business email that existed only in a panel, not the bio, confirming both sources matter
- Bulk mode: give it a game/category and it discovers the top live channels there for you, then checks each one — built for sponsorship-outreach list-building
- No account, login, or API key required
- Honest results: a channel with no public email returns `emailFound: false` rather than a guess or a fabricated value

### How it works

Pick a `mode`:

1. **`channel`** — check one or more specific channel logins.
2. **`by-game`** — discover the top live channels in a game/category, then check each one for a public email.

### Input

**Specific channels:**

```json
{ "mode": "channel", "logins": ["pokimane", "shroud"] }
```

**Top channels in a category:**

```json
{ "mode": "by-game", "gameName": "Just Chatting", "limit": 30 }
```

| Field | Type | Description |
|---|---|---|
| `mode` | string | `"channel"` (default) or `"by-game"`. |
| `login` / `logins` | string / array | `channel` mode — channel login(s) to check. |
| `gameName` | string | `by-game` mode — exact game/category name as shown on Twitch. |
| `limit` | integer | `by-game` mode — how many top live channels to check. Max 30 (Twitch's own ceiling). |
| `maxConcurrency` | integer | How many channels to check in parallel. Default 4. |
| `proxyConfiguration` | object | Apify Proxy settings. Residential is on by default. |

### Output

One record per checked channel:

```json
{
  "_input": "pokimane",
  "_source": "S1-gql",
  "_scrapedAt": "2026-08-25T20:20:26Z",
  "login": "pokimane",
  "displayName": "pokimane",
  "emails": ["teampokimane@wmeagency.com"],
  "emailFound": true,
  "emailSources": [
    { "field": "description", "emails": ["teampokimane@wmeagency.com"] }
  ],
  "description": "hi ♡ i stream sometimes 📧 Business inquiries: teampokimane@wmeagency.com"
}
```

A channel with no public email:

```json
{
  "_input": "shroud",
  "_source": "S1-gql",
  "_scrapedAt": "2026-08-25T20:20:30Z",
  "login": "shroud",
  "displayName": "shroud",
  "emails": null,
  "emailFound": false,
  "emailSources": null,
  "description": "I'm back baby"
}
```

A record with `_error` instead means that lookup failed (`"_error": "channel_not_found"` for a login that doesn't exist, or `"_error": "game_not_found_or_empty"` for a category with no live channels in `by-game` mode).

### Known limits

- **Only finds what streamers have chosen to publish.** Most channels don't list a public email at all — that's the honest, common outcome (`emailFound: false`), not a failure of this actor.
- **Doesn't follow outbound links.** A panel's `linkURL` (e.g. a Linktree page) is not crawled — this actor only reads Twitch's own bio/panel text, not third-party destination pages.
- **`by-game` mode checks at most the top 30 live channels** in a category per run — Twitch's own platform enforces this ceiling for anonymous/HTTP-only access.

### A note on use

This actor surfaces email addresses that account holders have deliberately made public for the purpose of being contacted about business opportunities. Please use the results responsibly and in line with applicable anti-spam laws (e.g. CAN-SPAM, GDPR/PECR) in your jurisdiction and the recipient's.

# Actor input Schema

## `mode` (type: `string`):

"channel" looks up specific channel login(s). "by-game" discovers the top live channels in a game/category first, then looks up each one -- useful for finding sponsorship-outreach targets in a niche.

## `login` (type: `string`):

"channel" mode -- a single Twitch channel login.

## `logins` (type: `array`):

"channel" mode only -- multiple channel logins to look up in one run.

## `gameName` (type: `string`):

"by-game" mode -- the exact game/category name as it appears on Twitch (e.g. "Just Chatting", "League of Legends"). The top live channels in this category (by current viewer count) will be looked up.

## `limit` (type: `integer`):

"by-game" mode only -- how many of the top live channels in the category to look up. Capped at 30 (Twitch's own per-page ceiling for this connection).

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

How many channels to look up in parallel.

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

Apify Proxy configuration. Residential is on by default.

## Actor input object example

```json
{
  "mode": "channel",
  "login": "pokimane",
  "gameName": "Just Chatting",
  "limit": 30,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

All scraped channel email-lookup records produced by this run.

# 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 = {
    "mode": "channel",
    "login": "pokimane",
    "gameName": "Just Chatting",
    "limit": 30,
    "maxConcurrency": 4,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("zucchini_gopher_m2v/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 = {
    "mode": "channel",
    "login": "pokimane",
    "gameName": "Just Chatting",
    "limit": 30,
    "maxConcurrency": 4,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("zucchini_gopher_m2v/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 '{
  "mode": "channel",
  "login": "pokimane",
  "gameName": "Just Chatting",
  "limit": 30,
  "maxConcurrency": 4,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call zucchini_gopher_m2v/twitch-email-scraper --silent --output-dataset

```

## MCP server setup

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