# Best Twitter Email Scraper (`scrapevanta/best-twitter-email-scraper`) Actor

Best Twitter Email Scraper helps you find publicly available email addresses from X (Twitter) profiles quickly and accurately. Extract emails, usernames, bios, follower counts, and website links for lead generation, outreach, sales prospecting, recruitment, and market research.

- **URL**: https://apify.com/scrapevanta/best-twitter-email-scraper.md
- **Developed by:** [ScrapeVanta](https://apify.com/scrapevanta) (community)
- **Categories:** Lead generation, Social media, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

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

## Best Twitter Email Scraper — Verified X / Twitter Email Leads, With the Query Report

Search X / Twitter by keyword for publicly listed email addresses, **verify every one**, and see the X / Twitter profile behind it — plus which of the search's own query templates actually produced the leads.

***

### What it does

#### 1. Every address is checked before you see it

Every address goes through the same checks:

| Check | What it answers |
|---|---|
| Syntax | Is this actually an address, or a fragment like `logo@2x.png`? |
| MX records | Does the domain publish mail servers and accept mail at all? |
| Role mailbox | Is this `info@`/`sales@`/`support@` — a desk rather than a person? |
| Free provider | Gmail, Outlook, Yahoo and several hundred others |
| Throwaway inbox | Known disposable-email providers, plus the public blocklist |
| Confidence | A 0–100 score combining all of the above |

Filter on any of them: `minimumConfidence`, `excludeRoleAccounts`, `excludeFreeProviders`, `excludeDisposableEmails`, `requireMxRecord`.

`requireMxRecord` drops addresses whose domain has no MX record **and** those where the lookup could not be completed — an unknown result is not evidence that a domain accepts mail.

#### 2. One inbox is counted once

De-duplication is on the canonical inbox, not the raw string. `J.Smith@Gmail.com`, `jsmith@gmail.com` and `j.smith+news@gmail.com` are one Gmail inbox and are returned once.

#### 3. The X / Twitter profile behind each address

The result link is parsed into the identity behind it:

- `profileHandle` — the account name
- `profileType` — what kind of page it is
- `profileUrl` — a canonical link to the profile
- `platformName` / `platformHost`

For example `https://twitter.com/jack` becomes handle `@jack` of type `profile`.

#### 4. Which query templates earned their cost

A run fires a grid of searches: every keyword against roughly thirty query templates against every `site:` pattern. Each one costs a SERP fetch. The run summary reports, per template:

| Field | Meaning |
|---|---|
| `pagesScanned` | Result pages fetched using this template |
| `resultsSeen` | Search results those pages contained |
| `addressesFound` | Addresses matched in them |
| `leadsReturned` | Addresses that survived verification and filters |
| `leadsPerPage` | The ratio worth comparing templates on |

`searchPatternsWithNoLeads` lists the templates that were searched and returned nothing usable, and every returned row carries the `searchPattern` that produced it. Narrow the next run to the templates that worked.

***

### Input

| Field | Type | Default | What it does |
|---|---|---|---|
| `keywords` | array | — | What to search for |
| `country` | string | United States | Which country's results to search |
| `emailType` | string | B2C | `B2B` returns company domains, `B2C` returns free-provider addresses |
| `maxEmails` | integer | 20 | Stop after this many |
| `verifyEmails` | boolean | true | Run the checks above |
| `minimumConfidence` | integer | 0 | Drop anything scoring lower |
| `excludeRoleAccounts` | boolean | false | Drop `info@`, `sales@`, … |
| `excludeFreeProviders` | boolean | false | Drop Gmail, Outlook, … |
| `excludeDisposableEmails` | boolean | true | Drop throwaway inboxes |
| `requireMxRecord` | boolean | false | Only domains that accept mail |
| `useDisposableBlocklist` | boolean | true | Load the public throwaway list |
| `includeResultSnippet` | boolean | true | Keep the text each address was found in |
| `emitRunSummary` | boolean | true | Append the totals and the template report |

***

### Output

```json
{
  "recordType": "lead",
  "platform": "X / Twitter",
  "searchKeyword": "fitness",
  "searchPattern": "email_for_bookings",
  "email": "hello@acmefitness.co.uk",
  "emailLocalPart": "hello",
  "emailDomain": "acmefitness.co.uk",
  "isValidSyntax": true,
  "isRoleAccount": true,
  "isFreeProvider": false,
  "isDisposable": false,
  "hasMxRecord": true,
  "mailServers": ["aspmx.l.google.com"],
  "emailCategory": "role",
  "confidence": 85,
  "profileHandle": "@jack",
  "profileType": "profile",
  "profileUrl": "https://twitter.com/jack",
  "sourceUrl": "https://twitter.com/jack",
  "resultTitle": "Acme Fitness"
}
```

A final `summary` record carries the run totals, the category breakdown, the top email domains and the per-template report.

***

### Good to know

- **This searches a public search engine for pages on X / Twitter.** It reads what is publicly indexed; it does not sign in to X / Twitter and cannot see anything private.
- **Only addresses that are already public are returned.** Nothing is guessed, generated or pattern-matched from a name.
- **Verification is a DNS check, not a mailbox check.** `hasMxRecord` says the domain accepts mail. It cannot say a specific inbox exists.
- **Coverage depends on what is indexed.** An address that appears nowhere in a public search result will not be found.
- Contact your prospects lawfully. Under GDPR, CAN-SPAM and similar rules you need a lawful basis for unsolicited contact, and the fact that an address is public is not on its own that basis.

# Actor input Schema

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

Enter one or more keywords to search for on X (Twitter).

## `country` (type: `string`):

Specify the country to target for Google search results.

## `scrapeFrom` (type: `string`):

Choose one option — All, Status, or Profile.

## `emailType` (type: `string`):

Choose one — B2C or B2B.

## `engine` (type: `string`):

Choose scraping engine. 🚀 Cost Effective (New): Uses residential proxies with async requests for faster, cheaper scraping. 🔧 Legacy: Uses GOOGLE\_SERP proxy with traditional selectors - more reliable but slower and more expensive.

## `maxEmails` (type: `integer`):

Enter the maximum number of emails to collect.

## `verifyEmails` (type: `boolean`):

Check each address: syntax, whether the domain publishes MX records and can receive mail at all, whether it is a throwaway inbox, a role mailbox or a free provider. Adds a DNS lookup per domain, cached across the run.

## `minimumConfidence` (type: `integer`):

Drop addresses scoring below this. A business address on a domain with MX records scores around 95; a role mailbox around 85; a throwaway 5.

## `excludeRoleAccounts` (type: `boolean`):

Drop info@, sales@, support@ and similar. They reach an organisation rather than a person.

## `excludeFreeProviders` (type: `boolean`):

Drop Gmail, Outlook, Yahoo and similar, keeping only company domains.

## `excludeDisposableEmails` (type: `boolean`):

Drop known temporary-email providers.

## `requireMxRecord` (type: `boolean`):

Drop addresses whose domain publishes no MX record, and those where the lookup could not be completed - an unknown result is not evidence the domain accepts mail.

## `useDisposableBlocklist` (type: `boolean`):

Download the public blocklist of disposable email domains at the start of the run, on top of the built-in set.

## `includeResultSnippet` (type: `boolean`):

Keep the search-result text each address was found in, so a lead can be checked in context.

## `emitRunSummary` (type: `boolean`):

Add a final record with totals, the category breakdown, top email domains, top profiles and how each query template performed.

## Actor input object example

```json
{
  "keywords": [
    "fitness",
    "gym",
    "workout"
  ],
  "country": "United States",
  "scrapeFrom": "All",
  "emailType": "B2C",
  "engine": "legacy",
  "maxEmails": 20,
  "verifyEmails": true,
  "minimumConfidence": 0,
  "excludeRoleAccounts": false,
  "excludeFreeProviders": false,
  "excludeDisposableEmails": true,
  "requireMxRecord": false,
  "useDisposableBlocklist": true,
  "includeResultSnippet": true,
  "emitRunSummary": true
}
```

# Actor output Schema

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

All scraped results, one dataset item per result.

# 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": [
        "fitness",
        "gym",
        "workout"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapevanta/best-twitter-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": [
        "fitness",
        "gym",
        "workout",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("scrapevanta/best-twitter-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": [
    "fitness",
    "gym",
    "workout"
  ]
}' |
apify call scrapevanta/best-twitter-email-scraper --silent --output-dataset

```

## MCP server setup

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