Twitter Email Scraper — X (Twitter) Profile & Lead Extractor (No Login)

Bulk-extract publicly listed contact emails from X / Twitter profiles — plus bio, follower / following / tweet counts, linked website, location, verified status and avatar. Drop in a list of @handles or profile URLs and get a clean, enriched, outreach-ready spreadsheet of X profiles. The Actor runs with no login, no cookies and no API key, reading only public profile data over residential proxies, and it parses the email/phone out of the public bio only — so there is zero risk to any X account and no access to private or hidden contact details.

🏆 Why this X profile scraper?

18+ fields per profile · thousands of profiles per run · email + phone parsed from the public bio · no browser (fast & cheap) · guest-token access = 0% ban risk · export to JSON / CSV / Excel. The unofficial X / Twitter API alternative for lead generation, influencer research and sales prospecting.

---

✨ What this Actor does / Key features

• 👤 Full public profile data — display name, @username, bio, location, join date (createdAt), avatar and verifiedType.
• 📊 Audience metrics — followers, following, tweetCount, likeCount, mediaCount and listedCount, read straight from X (no integer-overflow on huge accounts).
• ✉️ Contact extraction — email and phone parsed from the public bio, plus the linked website — the fields the official API does not hand you.
• 🎯 Contact-only filter — flip onlyWithContact to keep only profiles that expose an email or website, for clean, reachable lead lists.
• ⚡ No browser — pure lightweight API access; fast, cheap and scalable to thousands of handles.
• 🔁 Auto-dedupe & retries — handles are de-duplicated; failed lookups auto-retry on fresh proxy sessions.
• 🛡️ Login-free & safe — guest-token access over residential proxies. No account is used, so there is no ban risk.
• 📤 Any format — export to JSON, CSV, Excel or XML, or pull via the Apify API and webhooks.

🚀 Quick start (3 steps)

1. Configure — paste a list of X @handles or profile URLs into profiles (e.g. nasa, @naval, https://x.com/stripe).
2. Run — click Start. The Actor resolves each profile over a residential proxy and streams one clean record per profile into your dataset.
3. Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API.

📥 Input

Give the Actor at least one handle or URL in profiles. Everything else is optional.

Example — enrich a handle list (lead generation)

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

Example — keep only reachable profiles (email or website)

{
  "profiles": ["nasa", "spacex", "openai", "vercel", "supabase"],
  "onlyWithContact": true,
  "maxConcurrency": 6,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Example — large run with a result cap

{
  "profiles": ["handle1", "handle2", "handle3", "…"],
  "onlyWithContact": true,
  "maxResults": 2000,
  "maxConcurrency": 10
}

Field	Type	Description
profiles	array	X @handles or profile URLs (nasa, @naval, https://x.com/stripe). Required.
onlyWithContact	boolean	Keep only profiles that expose an email or website in the bio. 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.

📤 Output

One row per profile — 18+ fields, exportable to JSON, CSV, Excel or XML. Here is a trimmed sample 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/…/avatar.jpg",
  "url": "https://x.com/naval"
}

Note on contact data: the Actor only reads what a user has published in their public bio/website. It does not reveal private, hidden or account-gated emails or phone numbers. Many accounts list only a website (captured in website); email / phone are populated solely when the user placed them in their public profile.

⚙️ 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 (guest-token access).
3. It parses the public profile and extracts email / phone / website from the bio text.
4. It applies your filters (onlyWithContact, maxResults) and streams one clean, de-duplicated record per profile to the dataset.

No login, no cookies, no API keys — and no X account is ever used or risked.

💡 Use cases

• Lead generation & sales — turn handle lists into enriched contact databases with email, website and reach.
• Influencer marketing — vet creators by followers, niche and verifiedType before outreach.
• Recruiters & growth teams — enrich prospects with their X presence and linked website.
• Market & competitor research — snapshot the accounts in a niche and compare audience metrics over time.
• List cleaning — use onlyWithContact to keep only reachable profiles and skip dead handles.

👥 Who uses it

Lead-gen & sales teams · agencies and growth marketers · influencer-marketing platforms · recruiters and talent sourcers · analysts and researchers mapping a market or niche on X.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the profiles you enrich, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

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 public bio, which the API does not hand you. It effectively works as an unofficial X / Twitter API alternative for profile data.

Can I scrape Twitter without an API key or login? Yes. The Actor reads only public profiles over residential proxies using guest access, so there is no API key, no login and no cookies — and no X account is ever risked. You only need an Apify account.

Will every profile have an email? No — only profiles that publish one in their public bio. Many accounts expose a website instead, which is captured too. Turn on onlyWithContact to keep only profiles that are actually reachable. The Actor never exposes private or hidden contact details.

How many Twitter profiles can I scrape at once? Thousands. Pass a large profiles list and results stream into the dataset as they are collected, de-duplicated automatically.

Are the follower counts accurate? Yes — they are read straight from X's profile data, with no integer-overflow issues even for very large accounts.

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 XML, or pull via API and webhooks — a ready-made Twitter profile data export.

How do I get only X profiles that have a contact email or website? Turn on onlyWithContact and the Actor keeps just the profiles that expose an email or website link in their bio, giving you a clean, reachable lead list.

Is this legal and GDPR-compliant? The Actor collects only publicly available profile data that users chose to publish. You are responsible for complying with X's Terms and applicable privacy laws (GDPR / CCPA) — including having a lawful basis for processing any personal data such as bio emails, and honoring opt-outs. Use it responsibly.

🔗 More lead-gen & website data tools by logiover

Pair this X profile scraper with the rest of the lead-generation & web-data suite:

Tool	Actor
🕸️ Website contacts	Website Contact Scraper · B2B Lead Scraper
🔎 Social profiles	Bulk Social Profile Extractor
🐦 X / Twitter	X (Twitter) Tweet Scraper · X Post URL Scraper
🎵 TikTok	TikTok Profile Email Scraper
▶️ YouTube	YouTube Creator Email Finder
✉️ Email hygiene	Bulk Email Verifier · Bulk Email Deliverability Checker
🌐 Site intel	Website Tech Stack Detector · Subdomain Finder
📇 Leads engine	Leads Scraper

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to refresh your lead lists daily or weekly. Export results to JSON, CSV or Excel, sync to Google Sheets or your CRM, or push to your database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to build automated lead-enrichment pipelines.

⭐ Support & feedback

Found a bug or need an extra field? Open an issue on the Issues tab — response is usually fast. If this Actor saves you time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor collects only publicly available profile data that users have chosen to publish. It does not access private, hidden or account-gated information. You are responsible for complying with X's Terms of Service, GDPR / CCPA and any applicable privacy laws when processing personal data such as emails from bios.

---

📝 Changelog

2026-07-06

• ✨ README overhaul: richer output sample with real field names, three ready-to-run example scenarios, lead-gen cross-promo suite links, badges, and clearer public-data / privacy framing.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data within the 5-minute quality window; sharpened Store SEO metadata and expanded the FAQ with high-intent long-tail questions.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-28

• Health check passed — Actor verified working end-to-end on the Apify platform; changelog refreshed for Store quality compliance.

2026-06-20

• Maintenance & reliability pass: re-verified end-to-end against live data; refreshed the prefilled example input and tuned run defaults for faster, lower-cost runs.

2026-06-15

• Hardened X engine: retry + fresh-proxy rotation on connection drops during queryId extraction, plus built-in fallback queryIds — fixes intermittent socket-disconnect crashes.

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.