X (Twitter) Follower list API

Q: How do I get the followers list of an X (Twitter) account?

Send the account's handle as username, for example nasa or @nasa, and do not pass the full x.com profile link. Each row then describes one follower with username, name, url and location, and id is that follower's unique ID on X, the key to store when you compare lists taken on different days.

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Map the audience of an X (Twitter) account through its followers, each with bio, location, counts, verification and protected status. The list covers followers X makes visible and may be partial; the counts on each row belong to that follower.

X (Twitter) Follower list returns the accounts that follow one X account, given its username. Each row is one follower: the handle, the display name in name, the profile link, location passed through as written, that follower's own follower, following and post counts, verification, whether the account is protected, and when it was created. Social media managers, audience researchers and brand teams use it to see who an account's audience is: profiling the followers of a brand or creator, spotting influential followers worth engaging, or comparing the audiences of two accounts.

Pass the handle, with or without the @, and never the full profile link. Every count on a row belongs to the follower on that row, not to the account you asked about. The list holds the followers X makes visible, which may not be every follower, so read it as a view of the audience rather than a full census. created_at helps you flag clusters of newly created accounts when you audit an audience.

Price $0.56 per 1,000 requests ($0.000556 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra X (Twitter) Follower list endpoint (twitter/followers_list).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to twitter and action to followers_list, and put the parameters inside params.
- Required parameters:
  - username: X username, optionally prefixed with @, without entering a full profile URL. profile compiles data from author details within recent posts.
- Optional parameters:
  - limit: The most rows to return in this call, an integer from 1 to 2000. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 200)
- Returns a list of records. Main fields of each record: id, username, url, name, text, location, avatar_url, follower_count, following_count, post_count, is_verified, is_protected; 13 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=twitter.
- Example request body:
{
  "platform": "twitter",
  "action": "followers_list",
  "params": {
    "username": "nasa"
  }
}
- Price: $0.56 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`twitter`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`followers_list`	Capability identifier, fixed value.
`username`	body.params	Not declared	Yes	-	X username, optionally prefixed with @, without entering a full profile URL. profile compiles data from author details within recent posts; followers_list and following_list retrieve visible followers and following accounts respectively.
`limit`	body.params	`integer (1–2000)`	No	`200`	The most rows to return in this call, an integer from 1 to 2000. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "twitter",
  "action": "followers_list",
  "params": {
    "username": "nasa"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Real response

Captured September 26, 2026 at 08:56 (UTC) by calling this API with the parameters in the code sample above. results and count are that call's real response with personal information (names, handles, avatars, profile links, contact details) removed; the list keeps the first 2. id, billing and quota differ on every call, so only their shape is shown.

json

{
  "id": "req_…",
  "platform": "twitter",
  "action": "followers_list",
  "results": [
    {
      "id": "（已隐去）",
      "username": "（已隐去）",
      "url": "https://x.com/（已隐去）",
      "name": "（已隐去）",
      "text": "",
      "avatar_url": "https://pbs.twimg.com/（已隐去）",
      "follower_count": 0,
      "following_count": 6,
      "post_count": 0,
      "is_verified": false,
      "is_protected": false,
      "created_at": "Tue Aug 25 06:17:15 +0000 2026",
      "platform": "twitter"
    },
    {
      "id": "（已隐去）",
      "username": "（已隐去）",
      "url": "https://x.com/（已隐去）",
      "name": "（已隐去）",
      "text": "",
      "avatar_url": "https://abs.twimg.com/（已隐去）",
      "follower_count": 0,
      "following_count": 25,
      "post_count": 0,
      "is_verified": false,
      "is_protected": false,
      "created_at": "Sat Sep 26 10:42:56 +0000 2026",
      "platform": "twitter"
    }
  ],
  "count": 200,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`username`	Username (@handle).
`url`	Link to the record on the platform.
`name`	Name of the object itself, for account, product and business capabilities.
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`location`	Location description passed through as is; the format varies by platform.
`avatar_url`	Avatar image link. Some platforms return sized CDN links that can expire.
`follower_count`	Followers. null means not disclosed, not 0.
`following_count`	Accounts followed. null means not disclosed, not 0.
`post_count`	Total posts. null means not disclosed, not 0.
`is_verified`	Whether the platform verified the account. null means it cannot be determined.
`is_protected`	Keeps the platform's own meaning
`created_at`	Creation time, same format as posted_at.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).

FAQ

How do I get the followers list of an X (Twitter) account?

Send the account's handle as username, for example nasa or @nasa, and do not pass the full x.com profile link. Each row then describes one follower with username, name, url and location, and id is that follower's unique ID on X, the key to store when you compare lists taken on different days.

Whose numbers are `follower_count` and `post_count` on each row?

They belong to the follower on that row, not to the account you looked up. Sort by follower_count to find the most-followed people in an audience, and treat null as undisclosed rather than zero. For the looked-up account's own totals, call the X (Twitter) Details capability with the same handle.

How do I get the list of accounts someone follows?

Use the X (Twitter) Following list capability. It takes the same username and returns rows with the same fields, one per followed account. Reading both lists for one account shows its mutual connections: the handles that appear in both.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

X: Direction of Followers vs. Following ↗
X separately explains who follows you and who you follow, as following does not need to be mutual; protected posts have additional access restrictions. List queries are not bulk-follow actions and do not imply expanded access permissions.
Checked 2026-09-04