X / Twitter API

X / Twitter Followers API

Fetch the follower list of any public X (Twitter) account by username with cursor pagination. Limit is a per-page maximum and a native page holds up to 200 accounts; follow the response's nextCursor for more.

$0.45/1k req, pay per request, no subscription.

What the API returneditems[0]
{
"username": "joyriverabot",
"name": "Joy Rivera",
"bio": "Aerospace engineer. Mars rover ops. Views my own.",
"followers": 8420,
"following": 612,
"verified": false,
"location": "Pasadena, CA",
"avatarUrl": "https://pbs.twimg.com/profile_images/1758000001000000000/joy_rivera.jpg",
... 2 more fields
}
Uptime
100.00%
30d · 130,082 calls
Requests
130,083
30d · weekly, last 12 wks
Response
1.7s
median · 30d

Pricing and providers

X / Twitter Followers API pricing: one API, 2 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$4.50
$0.45/1k req, only for what you use. No monthly plan.
Your first 222 requests are free with the $0.10 starting balance.

Try it

Get X / Twitter followers in one request

requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `bio`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.
Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 14 of 15 fields. See every field

{
  "found": true,
  "data": {
    "items": [
      {
        "username": "joyriverabot",
        "name": "Joy Rivera",
        "bio": "Aerospace engineer. Mars rover ops. Views my own.",
        "followers": 8420,
        "following": 612,
        "verified": false,
        "location": "Pasadena, CA",
        "avatarUrl": "https://pbs.twimg.com/profile_images/1758000001000000000/joy_rivera.jpg",
        "id": "1290345678901234567",
        "createdUtc": 1596240000
      },
      {
        "username": "starfielddan",
        "name": "Dan Whitfield",
        "bio": "Amateur astronomer, telescope builder, dark sky chaser.",
        "followers": 15300,
        "following": 891,
        "verified": true,
        "location": "Flagstaff, AZ",
        "avatarUrl": "https://pbs.twimg.com/profile_images/1758000002000000000/dan_whitfield.jpg",
        "id": "884512345678901248",
        "createdUtc": 1500854400
      },
      {
        "username": "lunarlogbook",
        "name": "Lunar Logbook",
        "bio": "",
        "followers": 204,
        "following": 88,
        "verified": false,
        "location": "",
        "avatarUrl": "https://pbs.twimg.com/profile_images/1758000003000000000/lunar_logbook.jpg",
        "id": "1650123456789012480",
        "createdUtc": 1681257600
      }
    ],
    "nextCursor": "DAABCgABGZ5abcXYZ1234ABAAA"
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • usernamestring

    nasa

    The X (Twitter) username to fetch followers for, without the @ prefix (e.g. elonmusk).

  • cursorstring

    Opaque pagination cursor from a previous response's nextCursor. Omit for the first page; pass it to fetch the next page of followers.

  • limitinteger

    200

    Accepted but does not change the page: every call returns one full native page of followers (up to 200, depending on the source), never trimmed, so follow nextCursor to continue exactly where this response ended.

  • requireFieldsarray

    Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `bio`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a profile that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge. On a paginated walk it applies to the first page only; later pages stay with the source that page chose, at the price it was quoted.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

each itemdata.items[]

Follower records, normalized to a compact shape. Populated whenever the provider has data for the entity.

  • avatarUrlstring

    https://pbs.twimg.com/profile_images/1758000001000000000/joy_rivera.jpg

    URL of the account's profile image (may be empty). Populated whenever the provider has data for the entity.

  • biostringcan require

    Aerospace engineer. Mars rover ops. Views my own.

    The account's profile bio/description.

  • createdUtcnumber

    1596240000

    UTC epoch timestamp in seconds (Unix time) the account was created. Multiply by 1000 for a JS Date in milliseconds.

  • followersinteger

    8420

    How many followers this account has.

  • followingintegercan require

    612

    How many accounts this account follows.

  • idstring

    1290345678901234567

    Numeric X user id of the account, as a string.

  • locationstring

    Pasadena, CA

    The account's self-reported location (may be empty).

  • namestring

    Joy Rivera

    The account's display name. Populated whenever the provider has data for the entity.

  • usernamestring

    joyriverabot

    The account's @ handle, without the @ prefix. Populated whenever the provider has data for the entity.

  • verifiedboolean

    false

    Whether the account is verified.

datadata
  • nextCursorstring

    DAABCgABGZ5abcXYZ1234ABAAA

    Opaque cursor for the next page of followers, or null when there are no more. Pass it back as cursor to continue.

top level
  • foundboolean

    true

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the X / Twitter Followers API

The AnyAPI X / Twitter Followers API returns X / Twitter followers data as normalized JSON from one POST call to /v1/run/twitter.followers. Fetch the follower list of any public X (Twitter) account by username with cursor pagination. Limit is a per-page maximum and a native page holds up to 200 accounts; follow the response's nextCursor for more. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $0.45 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of X / Twitter followers calls through AnyAPI succeeded, with a median response time of 1.7 seconds across 130,082 measured calls.

It costs from $0.45 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Fetch the follower list of any public X (Twitter) account by username with cursor pagination. Limit is a per-page maximum and a native page holds up to 200 accounts; follow the response's nextCursor for more. The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of X / Twitter followers calls through AnyAPI succeeded, with a median response time of 1.7 seconds across 130,082 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 222 X / Twitter Followers calls at $0.00045 each.

AnyAPI asks the next of its 2 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/twitter.followers with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.