# Twitter Email Scraper - X Profile & Lead Extractor (`logiover/x-profile-email-scraper`) Actor
X / Twitter profile scraper & unofficial API: extract bio emails, follower counts and websites, export profiles to CSV/JSON. No login or API key.
- **URL**: https://apify.com/logiover/x-profile-email-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** Social media, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, NaN 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/platform/actors/running/actors-in-store#pay-per-event
## What's an Apify Actor?
Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases.
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.
In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md):
```bash
npm install apify-client
```
In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md):
```bash
pip install apify-client
```
In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md):
````bash
# MacOS / Linux
curl -fsSL https://apify.com/install-cli.sh | bash
# Windows
irm https://apify.com/install-cli.ps1 | iex
```bash
In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md).
If your project is in a different language, use 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
## Twitter Email Scraper — X (Twitter) Profile & Lead Extractor
#### Bulk-extract emails from public X / Twitter profiles — plus bio, followers, website, location & phone. No login.
**Drop in a list of @handles → get a clean, enriched spreadsheet of X profiles with contact details.**
Built for lead generation, influencer research, sales prospecting and competitive analysis.
---
### 📌 Overview
The **X (Twitter) Profile & Email Scraper** extracts complete public profile data
from any list of X / Twitter **@handles or profile URLs**. For each account it
returns the bio, **follower / following / tweet counts**, linked **website**,
location, verified status, account age and avatar — and it automatically parses a
**contact email and phone number** out of the bio so your list is outreach-ready.
It runs with **no login, no cookies and no API key**, accessing only public data
through residential proxies — so there is **zero risk to any X account**. And
because it uses lightweight API calls instead of a headless browser, it is one of
the **fastest and most cost-efficient** Twitter scrapers you can run at scale.
> ✅ **Enrich thousands of X profiles in a single run** — perfect for building
> influencer lists, sales prospects and market maps.
---
### ✨ Features
| | Feature | Description |
|---|---|---|
| 👤 | **Full profile data** | Name, @handle, bio, location, join date, avatar, verified type. |
| 📊 | **Audience metrics** | Followers, following, tweets, likes, media & listed counts. |
| ✉️ | **Contact extraction** | Email & phone parsed from the bio, plus the linked **website**. |
| 🎯 | **Contact-only filter** | Keep only profiles that expose an email or website. |
| ⚡ | **No browser** | Pure API access — fast, cheap, scalable to thousands of handles. |
| 🔁 | **Auto-dedupe & retries** | Handles are de-duplicated; failed lookups auto-retry on fresh sessions. |
| 🛡️ | **Login-free & safe** | Guest-token access over residential proxies — no account, no ban risk. |
| 📤 | **Any format** | Export to JSON, CSV, Excel, HTML or pull via API & webhooks. |
---
### 🎯 Who it's for
- **Lead generation & sales** — turn handle lists into enriched contact databases.
- **Influencer marketing** — vet creators by follower count, niche & reach before outreach.
- **Recruiters & growth teams** — enrich prospects with their X presence and website.
- **Analysts & researchers** — snapshot accounts in a market or niche over time.
---
### 🧾 Input
| Field | Type | Description |
|-------|------|-------------|
| `profiles` | array | **Required.** X @handles or profile URLs (`nasa`, `@naval`, `https://x.com/stripe`). |
| `onlyWithContact` | boolean | Keep only profiles with an email or website. Default `false`. |
| `maxConcurrency` | integer | Profiles fetched in parallel (1–12). Default `5`. |
| `maxResults` | integer | Stop after saving this many profiles. `0` = all. |
| `proxyConfiguration` | object | Residential proxy (required by X). Pre-configured for you. |
#### Example input
```json
{
"profiles": ["naval", "@paulg", "https://x.com/stripe"],
"onlyWithContact": false,
"maxConcurrency": 6
}
````
***
### 📦 Output
Each profile is saved as one structured record:
```json
{
"userId": "745273",
"username": "naval",
"name": "Naval",
"bio": "Angel investor. Building something new. Questions: hello@example.com",
"location": "Silicon Valley",
"website": "https://nav.al",
"email": "hello@example.com",
"phone": null,
"followers": 3369907,
"following": 921,
"tweetCount": 27042,
"likeCount": 14210,
"mediaCount": 980,
"listedCount": 31200,
"verified": true,
"verifiedType": "Blue",
"protected": false,
"createdAt": "Tue Mar 17 03:43:00 +0000 2009",
"profileImage": "https://pbs.twimg.com/profile_images/...",
"url": "https://x.com/naval"
}
```
#### 📖 Output field reference
| Field | Description |
|-------|-------------|
| `username` / `name` | Handle and display name |
| `bio` | Profile description |
| `location` | Self-reported location |
| `website` | Linked website (great B2B signal) |
| `email` / `phone` | Contact details parsed from the bio |
| `followers` / `following` | Audience size and following count |
| `tweetCount` / `likeCount` / `mediaCount` / `listedCount` | Activity metrics |
| `verified` / `verifiedType` | Verified status (e.g. Blue, Business, Government) |
| `protected` | Whether the account is private |
| `createdAt` | Account creation date |
| `profileImage` / `url` | Avatar URL and profile URL |
***
### ⚙️ How it works
1. You provide a list of X **@handles or profile URLs**.
2. The actor resolves each profile through X's public data layer over a residential proxy.
3. It parses the profile and extracts **email / phone / website** from the bio.
4. It applies your filters and streams one clean record per profile to the dataset.
No login, no cookies, no API keys — and **no X account is ever used or risked**.
***
### ❓ FAQ
#### Is this an X / Twitter API alternative for lead generation?
Yes. It turns a list of @handles into an enriched contact spreadsheet without the
official X / Twitter API, a developer account or app keys — and it parses emails
and phone numbers straight from the bio, which the API does not hand you.
#### Does it need login or cookies?
No. The Actor reads only **public** profile data via guest access — no login, no
cookies you provide, no developer API key. Nothing is tied to your X account, so
there's zero ban risk.
#### Will every profile have an email?
Only profiles that publish one in their bio. Many accounts expose a **website**
instead, which is captured too. Flip `onlyWithContact` on to keep only profiles
that are actually reachable — perfect for clean lead lists.
#### How many Twitter profiles can I scrape at once?
Thousands. Pass a large `profiles` list and results stream into the dataset as
they're collected, deduplicated automatically.
#### Are the follower counts accurate?
Yes — they're read straight from X's profile data, with no integer-overflow
issues even for very large accounts.
#### Is this an X / Twitter unofficial API for profile data?
Effectively, yes. It returns structured profile records — bio, follower counts,
website, location and verified status — without the official X API, a developer
account or app keys, so you can pull Twitter profile data programmatically.
#### How do I export Twitter profiles to CSV or JSON?
Every run streams clean records to a dataset you can download as CSV, JSON, Excel
or HTML, or pull via API and webhooks — a ready-made Twitter profile data export.
#### Can I scrape Twitter without an API key or login?
Yes. The actor reads public profiles over residential proxies using guest access,
so there's no API key, no login and no cookies — and no X account is ever risked.
***
### 🔗 Works great with
- 🐦 **X (Twitter) Tweet Scraper** — pull each profile's tweets and engagement.
- 🐦 **X (Twitter) Post Scraper by URL** — grab specific posts in bulk.
***
**X Profile Scraper · Twitter Profile Scraper · X Email Scraper · Twitter Lead Generation · No-login Twitter data export · Twitter unofficial API · Export Twitter profiles to CSV · Twitter bio email extractor · Scrape Twitter without API key**
⚖️ Collects publicly available profile data only. You are responsible for compliance with X's Terms, GDPR/CCPA and applicable privacy laws.
### 📝 Changelog
#### 2026-06-07
- Docs: added coverage for using the actor as a Twitter unofficial API, exporting profiles to CSV/JSON, and scraping Twitter without an API key.
#### 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.
# Actor input Schema
## `profiles` (type: `array`):
X / Twitter @handles or profile URLs. Examples: 'nasa', '@naval', 'https://x.com/stripe'.
## `onlyWithContact` (type: `boolean`):
Keep only profiles that expose a contact email or website link in their bio.
## `maxConcurrency` (type: `integer`):
How many profiles to fetch in parallel.
## `maxResults` (type: `integer`):
Stop after saving this many profiles. 0 = all.
## `proxyConfiguration` (type: `object`):
X requires residential proxies. Leave the default (Apify Proxy · RESIDENTIAL group).
## Actor input object example
```json
{
"profiles": [
"nasa",
"https://x.com/stripe"
],
"onlyWithContact": false,
"maxConcurrency": 5,
"maxResults": 0,
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}
```
# Actor output Schema
## `username` (type: `string`):
@handle
## `name` (type: `string`):
Display name
## `followers` (type: `string`):
Follower count
## `email` (type: `string`):
Contact email
## `website` (type: `string`):
Linked website
## `url` (type: `string`):
Profile URL
# 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 '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"profiles": [
"nasa",
"naval"
],
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
};
// Run the Actor and wait for it to finish
const run = await client.actor("logiover/x-profile-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 '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = {
"profiles": [
"nasa",
"naval",
],
"proxyConfiguration": {
"useApifyProxy": True,
"apifyProxyGroups": ["RESIDENTIAL"],
},
}
# Run the Actor and wait for it to finish
run = client.actor("logiover/x-profile-email-scraper").call(run_input=run_input)
# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item)
# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start
```
## CLI example
```bash
echo '{
"profiles": [
"nasa",
"naval"
],
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}' |
apify call logiover/x-profile-email-scraper --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/?tools=logiover/x-profile-email-scraper",
"--header",
"Authorization: Bearer "
]
}
}
}
```
## OpenAPI specification
```json
{
"openapi": "3.0.1",
"info": {
"title": "Twitter Email Scraper - X Profile & Lead Extractor",
"description": "X / Twitter profile scraper & unofficial API: extract bio emails, follower counts and websites, export profiles to CSV/JSON. No login or API key.",
"version": "1.0",
"x-build-id": "8RanjcLcHA5i68jZU"
},
"servers": [
{
"url": "https://api.apify.com/v2"
}
],
"paths": {
"/acts/logiover~x-profile-email-scraper/run-sync-get-dataset-items": {
"post": {
"operationId": "run-sync-get-dataset-items-logiover-x-profile-email-scraper",
"x-openai-isConsequential": false,
"summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.",
"tags": [
"Run Actor"
],
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/inputSchema"
}
}
}
},
"parameters": [
{
"name": "token",
"in": "query",
"required": true,
"schema": {
"type": "string"
},
"description": "Enter your Apify token here"
}
],
"responses": {
"200": {
"description": "OK"
}
}
}
},
"/acts/logiover~x-profile-email-scraper/runs": {
"post": {
"operationId": "runs-sync-logiover-x-profile-email-scraper",
"x-openai-isConsequential": false,
"summary": "Executes an Actor and returns information about the initiated run in response.",
"tags": [
"Run Actor"
],
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/inputSchema"
}
}
}
},
"parameters": [
{
"name": "token",
"in": "query",
"required": true,
"schema": {
"type": "string"
},
"description": "Enter your Apify token here"
}
],
"responses": {
"200": {
"description": "OK",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/runsResponseSchema"
}
}
}
}
}
}
},
"/acts/logiover~x-profile-email-scraper/run-sync": {
"post": {
"operationId": "run-sync-logiover-x-profile-email-scraper",
"x-openai-isConsequential": false,
"summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.",
"tags": [
"Run Actor"
],
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/inputSchema"
}
}
}
},
"parameters": [
{
"name": "token",
"in": "query",
"required": true,
"schema": {
"type": "string"
},
"description": "Enter your Apify token here"
}
],
"responses": {
"200": {
"description": "OK"
}
}
}
}
},
"components": {
"schemas": {
"inputSchema": {
"type": "object",
"required": [
"profiles"
],
"properties": {
"profiles": {
"title": "X profiles",
"type": "array",
"description": "X / Twitter @handles or profile URLs. Examples: 'nasa', '@naval', 'https://x.com/stripe'.",
"items": {
"type": "string"
}
},
"onlyWithContact": {
"title": "Only profiles with email or website",
"type": "boolean",
"description": "Keep only profiles that expose a contact email or website link in their bio.",
"default": false
},
"maxConcurrency": {
"title": "Max concurrency",
"minimum": 1,
"maximum": 12,
"type": "integer",
"description": "How many profiles to fetch in parallel.",
"default": 5
},
"maxResults": {
"title": "Max results",
"minimum": 0,
"type": "integer",
"description": "Stop after saving this many profiles. 0 = all.",
"default": 0
},
"proxyConfiguration": {
"title": "Proxy",
"type": "object",
"description": "X requires residential proxies. Leave the default (Apify Proxy · RESIDENTIAL group).",
"default": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
]
}
}
}
},
"runsResponseSchema": {
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"actId": {
"type": "string"
},
"userId": {
"type": "string"
},
"startedAt": {
"type": "string",
"format": "date-time",
"example": "2025-01-08T00:00:00.000Z"
},
"finishedAt": {
"type": "string",
"format": "date-time",
"example": "2025-01-08T00:00:00.000Z"
},
"status": {
"type": "string",
"example": "READY"
},
"meta": {
"type": "object",
"properties": {
"origin": {
"type": "string",
"example": "API"
},
"userAgent": {
"type": "string"
}
}
},
"stats": {
"type": "object",
"properties": {
"inputBodyLen": {
"type": "integer",
"example": 2000
},
"rebootCount": {
"type": "integer",
"example": 0
},
"restartCount": {
"type": "integer",
"example": 0
},
"resurrectCount": {
"type": "integer",
"example": 0
},
"computeUnits": {
"type": "integer",
"example": 0
}
}
},
"options": {
"type": "object",
"properties": {
"build": {
"type": "string",
"example": "latest"
},
"timeoutSecs": {
"type": "integer",
"example": 300
},
"memoryMbytes": {
"type": "integer",
"example": 1024
},
"diskMbytes": {
"type": "integer",
"example": 2048
}
}
},
"buildId": {
"type": "string"
},
"defaultKeyValueStoreId": {
"type": "string"
},
"defaultDatasetId": {
"type": "string"
},
"defaultRequestQueueId": {
"type": "string"
},
"buildNumber": {
"type": "string",
"example": "1.0.0"
},
"containerUrl": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"ACTOR_COMPUTE_UNITS": {
"type": "integer",
"example": 0
},
"DATASET_READS": {
"type": "integer",
"example": 0
},
"DATASET_WRITES": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_READS": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_WRITES": {
"type": "integer",
"example": 1
},
"KEY_VALUE_STORE_LISTS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_READS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_WRITES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_INTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_EXTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_RESIDENTIAL_TRANSFER_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_SERPS": {
"type": "integer",
"example": 0
}
}
},
"usageTotalUsd": {
"type": "number",
"example": 0.00005
},
"usageUsd": {
"type": "object",
"properties": {
"ACTOR_COMPUTE_UNITS": {
"type": "integer",
"example": 0
},
"DATASET_READS": {
"type": "integer",
"example": 0
},
"DATASET_WRITES": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_READS": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_WRITES": {
"type": "number",
"example": 0.00005
},
"KEY_VALUE_STORE_LISTS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_READS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_WRITES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_INTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_EXTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_RESIDENTIAL_TRANSFER_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_SERPS": {
"type": "integer",
"example": 0
}
}
}
}
}
}
}
}
}
}
```