Twitter Followers Scraper Tool for Clean X Exports

A Twitter followers scraper is useful when you need a clean audience export instead of a screenshot or a hand-scrolled list. The practical job is not just collecting handles. It is collecting public account records with IDs, names, descriptions, follower counts, profile images, verification flags, websites, and enough source context to know where each row came from.

The X Twitter Followers Scraper is the browser workflow for that job. Add one or more targets, choose a bounded result count or scrape through pagination, run the job, and inspect the output as a table, collapsible JSON, or CSV.

This article focuses on the tool workflow. If you want the lower-level endpoint guide, read how to scrape Twitter following lists and followers as JSON.

The scraper supports the social graph targets that are most useful for audience research. You can paste full X URLs or use compact target paths when you already know the handle, list ID, or community ID.

• `handle/followers` exports public followers for a profile.
• `handle/following` exports accounts the profile follows.
• `handle/verified_followers` limits the follower workflow to blue-verified followers.
• `handle/affiliates` collects affiliated organization accounts when available.
• `lists/ID/members` exports accounts included in an X list.
• `lists/ID/followers` exports accounts that follow an X list.
• `communities/ID/members` exports members of an X community.

This matters because not every research question should start from a profile follower list. For competitor analysis, a following list may reveal vendors, partners, creators, and accounts the company monitors. For creator discovery, list members and community members can produce a cleaner starting set than a broad follower export.

Most jobs should start with a small bounded run. Set maxResults to a positive number, review the rows, and confirm that the target is right before launching a larger export. The table, JSON viewer, CSV export, and logs all update from the saved run, so you can test without losing the job record.

When the target is correct and you want the full available stream, enable scrape all. The scraper continues through pagination until the source ends or the run is stopped. For large exports, use a credit cap and the stop button in the logs view so the run remains controllable.

• Use max results for test runs, sampling, and predictable exports.
• Use scrape all only when the target has been validated.
• Use a credit cap when a profile, list, or community may be large.
• Stop a run from logs when the sample is already enough or the target was wrong.

The scraper normalizes public account data into rows that are useful in spreadsheets and pipelines. The exact columns are inferred from the JSON rows returned by the run, so CSV and table output stay aligned. The table improves readability with image previews, link styling, and formatted booleans or numbers, while CSV keeps raw values.

1{2  "blue_verified": true,3  "business_account": "",4  "can_dm": true,5  "created_at": "Sun Dec 06 23:33:02 +0000 2009",6  "description": "Best-Selling Author | Clinical Psychologist",7  "followers_count": 6174319,8  "friends_count": 1652,9  "location": "",10  "media_count": 7370,11  "name": "Dr Jordan B Peterson",12  "profile_image": "https://pbs.twimg.com/profile_images/...",13  "screen_name": "jordanbpeterson",14  "source_target": "@elonmusk followers",15  "statuses_count": 51532,16  "user_id": "95092020",17  "verified": false,18  "website": "http://jordanbpeterson.com/books"19}

The important field for analysis is often source_target. It lets you combine several targets in one run, export one CSV, and still know whether a row came from profile followers, following, list members, list followers, affiliates, or community members.

Use the browser tool when a human is exploring targets, comparing sample quality, or preparing a one-off CSV. It is faster to paste a few targets, preview rows, and download the result than to write job code before you know which target format is best.

Use direct API calls when the workflow is scheduled, embedded in your product, or controlled by an agent runtime. The tool and the API are complementary: the tool helps you design the collection job, and the endpoint docs show how to automate it.

The main endpoints behind these workflows are the Twitter Followers endpoint, Twitter Following endpoint, List Members endpoint, and Community Members endpoint.

A reliable research workflow starts narrow. Pick a known account, export a small sample from followers or following, then decide whether that surface contains the type of accounts you need. If it does, run a larger export and rank the rows outside the scraper.

• Start with a profile following list when you want relationship signals.
• Start with followers when you want the audience around a brand, creator, or competitor.
• Start with verified followers when the first pass should prioritize public high-signal accounts.
• Start with list members when someone has already curated a niche account set.
• Start with community members when the topic is organized around an X community.

After the first export, enrich only the accounts that deserve more work. For investigation-heavy workflows, pair the graph export with Twitter API research workflows. For ongoing monitoring, use the patterns in Twitter monitoring agents.

Agents should not browse X pages or build cursor logic inside a prompt. The safer pattern is to expose a small tool that calls a structured endpoint and keeps authentication, payment, cursor storage, retries, and spend rules in runtime code.

MintAPI paid endpoints follow the documented request flow. A normal call may return a 402 Payment Required challenge, then the runtime signs one accepted route and retries with payment. If you are building an OpenAI tool around this workflow, read OpenAI tools with a paid Twitter API.

1curl --request GET \2  --url 'https://api.mintapi.dev/api/twitter/followers?screenname=elonmusk&blue_verified=0' \3  --header 'Authorization: Bearer YOUR_API_KEY'

Start in the dashboard when you are still deciding which target is useful. Run a small bounded scrape, review the output columns, then download CSV or move the target into code. When the same job needs to run repeatedly, use the endpoint docs and keep pagination explicit in your worker or agent runtime.

For related social data workflows, compare this with API patterns for social media data and Twitter API social signal agents.