READ API LIVEBuild on /v1 for search, profiles, timelines, audience graph, and tweet context.READ DOCS
xfetch

Workflow · Twitter followers API

Twitter followers API for profile-ready audience lists

Read a public account's followers as normalized profile objects, keep the continuation token opaque, and feed each page into segmentation or graph analysis.

Open endpoint reference →

Copyable request + contract response example

Each page returns follower profiles and an opaque continuation token

The response example comes from the endpoint documentation manifest. The same OpenAPI schema covers profiles mode and the IDs-only variant.

GET/v1/users/{id}/followers
Enriched Reads
cURL
curl 'https://api.xfetch.io/v1/users/44196397/followers?mode=profiles' \
  -H "Authorization: Bearer $XFETCH_API_KEY"
Response example
{
  "data": [
    {
      "id": "95092020",
      "username": "jordanbpeterson",
      "name": "Dr Jordan B Peterson",
      "description": "Best-Selling Author | Clinical Psychologist | #1 Education Podcast | Co-founder of @petersonacademy | Order my new book \"We Who Wrestle With God\" here:",
      "created_at": "2009-12-06T23:33:02.000Z",
      "verified": true,
      "protected": false,
      "profile_image_url": "https://pbs.twimg.com/profile_images/1407056014776614923/TKBC60e1_normal.jpg",
      "follower_count": 6180030,
      "following_count": 1653,
      "tweet_count": 51532,
      "media_count": 7370
    }
  ],
  "meta": {
    "request_id": "req_01HXFETCHEXAMPLE",
    "credits": {
      "charged": 2,
      "remaining": 998
    },
    "pagination": {
      "next_token": "tok_2"
    }
  }
}

One workflow

Build an audience list one stable page at a time

The page uses profiles mode as one clear workflow: enrich an audience as you traverse it. IDs mode remains available when a lower-cost graph pass is the better first step.

  1. 01

    Resolve the account once and pass its numeric user ID.

  2. 02

    Request mode=profiles to receive normalized follower objects.

  3. 03

    Continue only when meta.pagination.next_token is present, passing it unchanged.

Code-derived cost

Profiles mode prices the follower objects returned

The rule and worked charge below come from the shared endpoint-pricing catalog used by billing and the API reference.

Current rule

1 base + 1 per item

This page's request uses profiles mode, so each returned follower profile is a priced item. IDs mode uses its separate block rule, shown on the pricing hub and endpoint reference.

Documented response example

2 credits

The example contains 1 primary record. Failed validation, authentication, insufficient-credit, rate-limit, service-side, and internal failures are not charged.

Estimate a monthly workloadSee every active pricing keySee the free starting credit grant

Related workflow context

Continue from this result

FAQ

Twitter Followers API questions

Can the Twitter Followers API return profiles instead of IDs?
Yes. Set mode=profiles for normalized user objects. Set mode=ids for ID objects when the graph itself is the immediate need.
How do I paginate followers?
When a response includes meta.pagination.next_token, pass that token unchanged as next_token on the next request. Stop when it is absent.
Can I set limit in profiles mode?
No. The limit parameter belongs to IDs mode. Profiles mode does not expose a public page-size control; continue with next_token.
Do IDs mode and profiles mode cost the same?
No. Each mode maps to its own public pricing key. This page derives the profiles-mode rule; the endpoint reference and pricing hub show both.

Run the documented workflow on your own key

Google sign-in opens the dashboard playground with this endpoint selected.

Compare API costs →