Twitter Profile Scraper | No Cookie | No Login
Pricing
from $4.00 / 1,000 results
Twitter Profile Scraper | No Cookie | No Login
Extract public Twitter/X profiles in bulk — followers, bio, location, verified status, join date, tweet counts & profile images. No API key, no login. Export to JSON, CSV, Excel or Google Sheets. Rotation-proof, ban-resistant, and reliable at scale.
Pricing
from $4.00 / 1,000 results
Rating
0.0
(0)
Developer
REXREUS D.O
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Twitter / X Profile Scraper 🐦 — Bulk Export Public X Profiles (No API Key, No Login)
Turn any list of X (Twitter) usernames into clean, structured profile data in seconds. Followers, bio, location, verified status, join date, tweet counts, profile images and more — exported straight to JSON, CSV, Excel or Google Sheets. No X API key. No login. No rate-limit headaches.
Built as an enterprise-grade scraper that reads the same public GraphQL responses your browser receives, and keeps working even when X rotates its internal query IDs.
✅ Public data only. This Actor scrapes information that is publicly visible on a profile page. It never logs in, never bypasses private/protected accounts, and never touches login-gated content.
💡 What can you do with it?
- Lead generation & sales — enrich a list of X handles with followers, bio and website.
- Influencer discovery — rank creators by follower count, verified status and niche.
- Competitor & brand monitoring — track audience size and profile changes over time.
- Market & audience research — build datasets of accounts in any industry.
- Data enrichment — append X profile fields to your CRM, spreadsheet or database.
⭐ Why choose this scraper
- No API key, no login — reads the same public data your browser sees.
- Rotation-proof — the internal query hash and guest token are captured live at runtime, never hardcoded. When X changes them, this Actor adapts automatically.
- Ban-resistant — realistic rotating browser fingerprints, residential proxy waterfall, a session pool binding token ↔ IP ↔ fingerprint, and exponential backoff. An empty result is treated as a block, never silently reported as "0 followers".
- Reliable, flat output — one clean row per profile with consistent types; missing
fields are
null, never dropped. A single failed handle never breaks the whole run. - Cost control —
maxItemscaps exactly how many records you pay for. - Scales cleanly — deterministic memory cleanup and streaming output for large runs.
🚀 How to use
- Click Try for free / Run.
- Add the X usernames you want in
handles(with or without@), or paste profile URLs intostartUrls. - (Optional) Set
maxItemsto cap results and pick your proxy. - Click Start — results stream into the dataset in real time.
- Export as JSON, CSV, Excel, HTML or Google Sheets, or pull them via the Apify API and integrations (Make, Zapier, n8n, webhooks, and more).
You can also schedule runs (daily/weekly) to keep your dataset fresh.
📥 Input
| Field | Type | Default | Description |
|---|---|---|---|
handles | string[] | – | X usernames (with or without @). e.g. ["nasa", "@github"] |
startUrls | array | – | Profile URLs, e.g. https://x.com/nasa. Strings or { "url": ... }. |
resultsMode | enum | profile_only | profile_only or profile_with_tweets. |
includeRecentTweets | boolean | false | Capture recent tweets (see Limitations). |
maxItems | integer | 0 | Max records to push (0 = unlimited). |
maxConcurrency | integer | 3 | Parallel browsers, clamped to 1–5. |
proxyConfiguration | object | residential | Apify proxy config. Residential is strongly recommended. |
At least one of handles or startUrls must be provided — the Actor fails fast with a
clear message otherwise.
Example input
{"handles": ["apify", "nasa", "github"],"resultsMode": "profile_only","maxItems": 3,"maxConcurrency": 2,"proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }}
📤 Output
Each profile becomes one flat dataset item:
{"rest_id": "11348282","username": "NASA","name": "NASA","description": "There's space for everybody. ✨","location": "Earth","url": "https://www.nasa.gov","followers_count": 95000000,"friends_count": 180,"statuses_count": 68000,"media_count": 24000,"favourites_count": 3200,"listed_count": 91000,"verified": false,"is_blue_verified": true,"protected": false,"created_at": "2007-12-19T20:29:24.000Z","profile_image_url": "https://pbs.twimg.com/profile_images/000/nasa.jpg","profile_banner_url": "https://pbs.twimg.com/profile_banners/000/nasa","recent_tweets": null,"sourceUrl": "https://x.com/nasa","scrapedAt": "2026-01-01T00:00:00.000Z","status": "ok","error": null}
Per-item status
Every target yields exactly one row — a failure never breaks the whole run:
| status | Meaning |
|---|---|
ok | Profile scraped successfully. |
protected | Account is private; public data unavailable. |
not_found | Handle does not exist / suspended. |
blocked | Anti-bot / rate-limit signal after retries were exhausted. |
challenge_failed | An interactive challenge could not be solved. |
❓ FAQ
Do I need a Twitter/X API key or an account? No. The Actor reads only public profile data — no API key, no login, no cookies.
Can it scrape private/protected accounts?
No. Protected accounts return status: "protected" with no private data. This Actor never
bypasses access controls.
How many profiles can I scrape?
As many as you like. Use maxItems to cap the run and control cost, and maxConcurrency
(1–5) to balance speed vs. stability.
Which proxy should I use? Residential proxies are strongly recommended — datacenter IPs are blocked by X within 1–2 requests.
In what formats can I export the data? JSON, CSV, Excel, HTML, RSS or Google Sheets — via the UI or the Apify API.
Can I automate or schedule it? Yes. Schedule recurring runs and connect the output to Make, Zapier, n8n, webhooks and more through Apify integrations.
⚠️ Limitations
- Recent tweets are not yet normalized into the output;
recent_tweetsis alwaysnullin this version even whenincludeRecentTweetsis enabled. Profile fields are the supported contract. - Datacenter proxies are blocked by X within 1–2 requests — use residential.
📜 Legal & responsible use
This Actor collects only publicly available data and does not circumvent authentication or access controls. You are responsible for how you use the output. Review X's Terms of Service and applicable data protection laws (e.g. GDPR/CCPA) before scraping, storing, or processing personal data. Do not use this Actor to harass, profile, or de-anonymize individuals.