X.com Profiles Scraper

X.com Profiles Scraper

Scrape X.com profiles from handles, user IDs, or direct URLs, up to a million per run. Every profile returns its bio, follower count, verification status, and professional category. No login or API key. Export to CSV, JSON, Excel, or XML.

X.com's official API requires a developer account, project approval, and strict rate limits that throttle profile lookups. This Actor reads the public profile pages directly, so you can collect data on any list of handles or user IDs without authentication. It returns each profile in a consistent, flat schema ready for analysis.

Who uses it	What they scrape X.com for
Market researchers	Build a dataset of influencer profiles in a niche to analyze audience size and engagement.
Lead generation teams	Verify the professional category and verification status of a list of prospect accounts.
Data journalists	Collect profile bios and follower counts from a list of public figures for a story.
Social media managers	Audit a competitor's follower list to understand their audience demographics.

What it does

This Actor collects X.com profile data from handles, user IDs, or direct URLs and returns each profile as a flat row.

• 🔍 Flexible input: Provide a list of handles, user IDs, or direct profile and tweet URLs.
• ✅ Verification filter: Optionally return only X Premium (blue check) accounts or only non-verified ones.
• 💼 Professional category filter: Narrow results to only 'Creator' or 'Business' account types.
• 📊 Flat output: Each profile is a single row with bio, followers, following, location, and more.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with X.com data

📈 Audit influencer rosters.

A marketing agency uploads a list of 500 handles to verify each account's follower count, blue-check status, and professional category before renewing a campaign.

🎯 Enrich lead lists.

A sales team runs a list of prospect user IDs through the scraper to pull bios, locations, and website links for account research.

📰 Profile public figures.

A journalist scrapes the profiles of 200 political candidates to compare their follower growth and bio changes over a campaign season.

🤖 Build a creator database.

A startup uses the 'Creator' filter to scrape thousands of profiles and build a searchable database of content creators by niche.

Why choose this scraper

	What you get
No API limits	Scrape up to a million profiles per run without rate limiting or developer accounts.
Simple input	Paste a list of handles or user IDs, or provide a spreadsheet of profile URLs.
Clean data	Get a structured dataset with consistent fields for every profile, ready for spreadsheets.

How it compares

No other Store actor targets X.com the same way, so the honest comparison is with the alternatives teams actually weigh.

	X.com Profiles Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When X.com changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Drive the Actor from a list of handles, user IDs, or direct profile URLs, and apply optional filters for verification status and professional category so only matching profiles reach your dataset. The Input tab lists every parameter.

A first run with the defaults:

{
  "maxItems": 10,
  "twitterHandles": [
    "elonmusk",
    "sama",
    "naval",
    "paulg",
    "garrytan",
    "vitalikbuterin",
    "jack",
    "barackobama",
    "billgates",
    "justinbieber",
    "taylorswift13",
    "rihanna",
    "selenagomez",
    "cristiano",
    "narendramodi",
    "potus",
    "cnn",
    "bbcworld",
    "nytimes",
    "reuters",
    "bloomberg",
    "nasa",
    "spacex",
    "tesla",
    "apple",
    "google",
    "microsoft",
    "amazon",
    "netflix",
    "openai",
    "ylecun",
    "karpathy",
    "sundarpichai",
    "tim_cook",
    "satyanadella",
    "jeffbezos",
    "shakira",
    "kimkardashian",
    "arianagrande",
    "drake",
    "beyonce",
    "katyperry",
    "arishlp",
    "jeffdean",
    "demishassabis",
    "ilyasut",
    "andrewyng",
    "pmarca",
    "balajis",
    "palmerluckey"
  ]
}

A larger pull:

{
  "maxItems": 200,
  "twitterHandles": [
    "elonmusk",
    "sama",
    "naval",
    "paulg",
    "garrytan",
    "vitalikbuterin",
    "jack",
    "barackobama",
    "billgates",
    "justinbieber",
    "taylorswift13",
    "rihanna",
    "selenagomez",
    "cristiano",
    "narendramodi",
    "potus",
    "cnn",
    "bbcworld",
    "nytimes",
    "reuters",
    "bloomberg",
    "nasa",
    "spacex",
    "tesla",
    "apple",
    "google",
    "microsoft",
    "amazon",
    "netflix",
    "openai",
    "ylecun",
    "karpathy",
    "sundarpichai",
    "tim_cook",
    "satyanadella",
    "jeffbezos",
    "shakira",
    "kimkardashian",
    "arianagrande",
    "drake",
    "beyonce",
    "katyperry",
    "arishlp",
    "jeffdean",
    "demishassabis",
    "ilyasut",
    "andrewyng",
    "pmarca",
    "balajis",
    "palmerluckey"
  ]
}

Pricing

Pay-per-result: $0.01734 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$1.73
1,000 results	$17.34
10,000 results	$173.40

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the X.com Profiles Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to X.com through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/x-com-profiles-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that you are using only one input method: either startUrls or twitterHandles/twitterUserIds, not both. Also, if you have filters enabled, they may be excluding all your input profiles. Try disabling the verification and professional type filters to see if data comes through.

The scraper is returning fewer profiles than I expected.

First, confirm that your maxItems setting is high enough. Then, check if any of your input handles or IDs are invalid, suspended, or private accounts, which cannot be scraped. The filters for blue verification and professional type will also reduce the output count.

I'm getting errors when using a list of tweet URLs.

Ensure the URLs are full, valid X.com or twitter.com links to specific tweets. The Actor extracts the profile from the tweet author, so deleted tweets or tweets from suspended accounts will fail. Try testing with a single, known working tweet URL first.

Some profile fields are empty in the output.

This is expected. Not every X.com user fills out their bio, location, website, or professional category. The Actor returns whatever is publicly available on the profile page, and empty fields mean the user left that section blank.

The run is slow or timing out.

Large profile lists can take time. Increase the run's memory or timeout in the Apify console settings. Using Apify's residential proxies can also improve reliability for very large scraping jobs.

FAQ

Question	Answer
Can I scrape profiles without a Twitter/X API key?	Yes. This Actor reads public profile pages directly and does not use the official API, so no developer account or API key is needed.
What is the difference between providing handles and user IDs?	Handles are the @usernames you see on the site, while user IDs are the numeric strings in a profile's URL. You can use either, or both together, and the Actor will resolve them to the same profile data.
Can I scrape profiles from a list of tweet URLs?	Yes. If you provide a tweet URL in the startUrls field, the Actor will extract the author's profile from that tweet and return the full profile data.
How do I filter for only verified accounts?	Set the 'Filter by Blue Verified' option to true. This will return only accounts that currently have an X Premium (blue check) verification badge.
What does the professional category filter do?	It lets you return only accounts that have set their profile type to 'Creator' or 'Business' on X.com. Leave it empty to get all account types.
Is there a limit on how many profiles I can scrape?	You can set the maximum profiles per run up to 1,000,000. The Actor will stop after collecting that many profiles, even if you provided more inputs.
Can I use both direct URLs and handle lists in the same run?	No. The startUrls field and the twitterHandles/twitterUserIds fields are mutually exclusive. Use one input method per run.
What data fields does the scraper return for each profile?	The output includes the handle, display name, bio, follower and following counts, location, website, join date, verification status, professional category, and profile image URL.
Does this scraper handle rate limiting or blocking by X.com?	The Actor runs on Apify's infrastructure with built-in proxy rotation and request management to minimize blocks. For large runs, using Apify proxy is recommended.
Can I export the scraped data to Google Sheets?	Yes. You can export your dataset to CSV, JSON, Excel, or XML, and Apify also offers integrations to send data directly to Google Sheets.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by X Corp. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.