Twitter Email Scraper - X Profile & Lead Extractor

---

📌 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

{
  "profiles": ["naval", "@paulg", "https://x.com/stripe"],
  "onlyWithContact": false,
  "maxConcurrency": 6
}

---

📦 Output

Each profile is saved as one structured record:

{
  "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.

---

📝 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.