---
title: "GET /twitter/user/followers_ids"
method: GET
path: "/twitter/user/followers_ids"
---

# GET /twitter/user/followers_ids

`GET /twitter/user/followers_ids`

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 (1 credit ≈ $0.00001)

| Returned IDs per call | Price | USD equivalent | Best for |
|---|---|---|---|
| 4,000 - 5,000 | **0.45 credits / ID** | **$0.0045 / 1k IDs** ($4.50 per million) | Bulk graph collection (recommended) |
| 200 - 3,999 | 1 credit / ID | $0.01 / 1k IDs | Medium-batch fetch |
| 50 - 199 | 2 credits / ID | $0.02 / 1k IDs | New-follower monitoring / frequent polling |

💡 **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`](/api-reference/endpoint/get_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`](/api-reference/endpoint/get_user_batch_info_by_ids).

## Query parameters

- `userName` string, string
- `userId` string, string
- `count` integer
- `cursor` string, string

## Response `200`

Follower IDs

- object
  - `ids` string[] — Array of follower IDs.
  - `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` 'success' | 'error' — Status of the request — 'success' or 'error'.
  - `msg` string — Status message.
  - `code` integer — Status code (0 = success).

## Other responses

- `400` — Missing or invalid parameter (e.g., neither userName nor userId provided, or userId not numeric).
- `502` — Upstream Twitter source temporarily unavailable.

---

[API](https://skmtc.net/twitterapi/apis/twitterapi-io-the-most-stable-fastest-cheapest-twitter-api.md) · [All operations](https://skmtc.net/twitterapi/apis/twitterapi-io-the-most-stable-fastest-cheapest-twitter-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/twitterapi/twitterapi-io-the-most-stable-fastest-cheapest-twitter-api/revisions/1b1afaf3df76/schema)