Twitter Followers API

Call GET /twitter/user/followers with the userName of the account you want, and read the followers array from the JSON response. To export the full list, omit the cursor on the first call, then pass the next_cursor value back on each following call and keep going until has_more comes back false. Each call is $0.001 and the v1 endpoint returns about 200 followers per page, so exporting 1,000 followers costs roughly $0.05. The result is structured JSON you can write straight to CSV or a database.

GetXAPI charges $0.001 per call. The v1 followers endpoint returns about 200 followers per call, so 1,000 followers costs roughly $0.05. There is no subscription and no minimum. The official X API gates follower lookups behind paid developer tiers with restricted access on lower plans, so GetXAPI is the cheapest managed path to export a follower list at volume.

Omit the cursor parameter on your first request to get page one. Each response includes a next_cursor token and a has_more flag. Pass next_cursor back in the cursor parameter on your next request to fetch the following page, and repeat the loop until has_more is false. That walks the entire follower list without holding any state on the server side. The same pattern works for following, verified followers, and mutuals.

Yes. GET /twitter/user/check_follow_relationship returns the follow relationship between two accounts in a single call, so you can confirm whether one user follows another without paging an entire list. For shared connections, POST /twitter/user/followers_you_know returns the followers you know in common, which is the mutuals view.

You do not need an X developer account or the official OAuth flow. You do need a GetXAPI key, which is a single Bearer token you copy after a 30-second signup. That key authenticates every followers and following request. There is no app review and no waiting period, so you can pull your first follower list in under a minute. You start with $0.10 in free credits, no card required.

The v1 followers endpoint returns about 200 followers per page, and followers_v2 returns about 70 per page with a richer profile payload per record. Both page through the full list with a cursor. Use v1 when you want the cheapest, fastest export of a large list, and v2 when you need more detail on each follower and are willing to make more calls to walk the same list.

Yes. Use GET /twitter/user/verified_followers to pull just the verified followers of an account, and GET /twitter/user/following (or following_v2) to pull the accounts that user follows. Both run on the same Bearer key and the same flat $0.001 per call, and both page with the same cursor pattern as the followers endpoint.