Twitter Followers API: Pull Any Account's List for $0.016/1K

Hit GET /twitter/user/followers and pass the userName of the target account. The response carries a followers array plus a next_cursor and a has_more flag. For a complete dump, leave cursor empty on the first request, feed next_cursor back on every subsequent request, and stop once has_more turns false. Each request costs $0.0008 and returns about 70 followers on the first page and fewer after that, so a 1,000-follower export takes roughly 20 calls and runs about $0.016. Everything comes back as clean JSON, ready to drop into CSV or a table.

Every call is a flat $0.0008. Calls return about 70 followers on the first page and fewer after that, so pulling 1,000 followers takes roughly 20 calls and lands around $0.016. No plan, no monthly floor, no commitment. The official X API hides follower reads behind paid developer tiers and blocks them entirely on cheaper plans, which makes TwitterAPIs the lowest-cost pay-as-you-go way to export a follower list at scale.

Leave the cursor parameter off your first request to land on page one. Every response ships a next_cursor token alongside a has_more flag. Drop that next_cursor into the cursor parameter on the next request to grab the following page, and keep looping while has_more stays true. The whole list comes out this way, with no state pinned on the server. Following, verified followers, and mutuals all page with the exact same mechanic.

Yes. GET /twitter/user/check_follow_relationship resolves the follow link between two accounts in one call, so you can verify whether user A follows user B without crawling a whole list. To find shared connections, POST /twitter/user/followers_you_know returns the followers the two accounts have in common, which is the mutuals view.

No X developer account and no official OAuth dance are involved. All you need is a TwitterAPIs key, a single Bearer token you grab after a 30-second signup, and it signs every followers and following request. Nothing waits on app review or approval, so your first follower pull can happen inside a minute. Signup also drops $0.50 of free credit into your account, with no card on file.

Both return about 70 followers on the first page and fewer on subsequent pages, so there is no page-size or cost difference between them. The difference is the response: followers_v2 attaches a fuller profile object to each record and has the more consistent cursor. Prefer v2 for new work. Use v1 only when you already have an integration built against its response shape. Note that the count parameter is currently ignored by both endpoints, so page size is fixed regardless of what you request.

Yes to both. GET /twitter/user/verified_followers narrows the result to an account's verified followers, while GET /twitter/user/following (or following_v2) returns the accounts that user follows. Each one authenticates with the same Bearer key, bills at the same flat $0.0008 per call, and pages with the identical cursor loop the followers endpoint uses.