Skip to main content
GET
cURL
Get a user’s follower IDs in bulk — lightweight, IDs only, no profile metadata. Designed for large-scale follower-graph collection where you join IDs against your own data warehouse. Up to 5,000 IDs per call. Pass either userName or userId. Use cursor from the previous response (next_cursor) to paginate.

Tiered pricing (per ID returned)

Credits ↔ USD: 100,000 credits = 1.00(1credit≈1.00 (1 credit ≈ 0.00001)
💡 Concrete examples at the bulk tier:
  • Pull a user’s 1 million followers for $4.50
  • Pull 100,000 followers for just $0.45
  • Pull a celebrity’s 10 million follower graph for $45
Minimum charge: 100 credits ($0.001) per call (50 IDs × 2 credits, the smallest page size).

When to use this vs /twitter/user/followers

  • This endpoint: returns IDs only, dramatically cheaper, up to 5,000 per call. Use for follower-ID collection at scale.
  • /twitter/user/followers: returns full follower profiles (name, bio, avatar, etc.), 200 max per call, $0.01 / 1k followers at max page. Use when you need profile data.
You can also combine: pull IDs cheaply here, then hydrate the IDs you care about via /twitter/user/batch_info_by_ids.

Authorizations

X-API-Key
string
header
required

Query Parameters

userName
string<string>

Screen name of the user (e.g. elonmusk). Either userName or userId is required.

userId
string<string>

Numeric user ID. Either userName or userId is required.

count
integer
default:5000

Number of follower IDs to return per page. Min 50, max 5000. Default 5000 (bulk pull, recommended).

Required range: 50 <= x <= 5000
cursor
string<string>

Pagination cursor — pass the next_cursor value from the previous response. First page: omit or pass empty string.

Response

Follower IDs

ids
string[]

Array of follower IDs.

Numeric Twitter user ID, returned as string to preserve precision (Twitter IDs exceed JS Number safe range).

has_next_page
boolean

True if more pages are available (next_cursor is non-empty and not '0').

next_cursor
string

Cursor for the next page. Empty string or '0' means no more pages.

status
enum<string>

Status of the request — 'success' or 'error'.

Available options:
success,
error
msg
string

Status message.

code
integer

Status code (0 = success).