> ## Documentation Index > Fetch the complete documentation index at: https://docs.twitterapi.io/llms.txt > Use this file to discover all available pages before exploring further. # Get User Followers IDs (Bulk) > 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). ## OpenAPI ````yaml GET /twitter/user/followers_ids openapi: 3.0.1 info: title: TwitterAPI.io the most stable/fastest/cheapest twitter api. description: Provide the most stable/fastest/cheapest twitter api. license: name: MIT version: 1.0.0 servers: - url: https://api.twitterapi.io security: - ApiKeyAuth: [] paths: /twitter/user/followers_ids: get: description: >- 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). parameters: - name: userName in: query description: >- Screen name of the user (e.g. `elonmusk`). Either `userName` or `userId` is required. schema: type: string format: string - name: userId in: query description: Numeric user ID. Either `userName` or `userId` is required. schema: type: string format: string - name: count in: query description: >- Number of follower IDs to return per page. Min 50, max 5000. Default 5000 (bulk pull, recommended). schema: type: integer default: 5000 minimum: 50 maximum: 5000 - name: cursor in: query description: >- Pagination cursor — pass the `next_cursor` value from the previous response. First page: omit or pass empty string. schema: type: string format: string responses: '200': description: Follower IDs content: application/json: schema: type: object properties: ids: type: array items: type: string description: >- Numeric Twitter user ID, returned as string to preserve precision (Twitter IDs exceed JS Number safe range). description: Array of follower IDs. has_next_page: type: boolean description: >- True if more pages are available (next_cursor is non-empty and not '0'). next_cursor: type: string description: >- Cursor for the next page. Empty string or '0' means no more pages. status: type: string description: Status of the request — 'success' or 'error'. enum: - success - error msg: type: string description: Status message. code: type: integer description: Status code (0 = success). '400': description: >- Missing or invalid parameter (e.g., neither userName nor userId provided, or userId not numeric). content: application/json: schema: $ref: '#/components/schemas/Error' '502': description: Upstream Twitter source temporarily unavailable. content: application/json: schema: $ref: '#/components/schemas/Error' components: schemas: Error: required: - error - message type: object properties: error: type: integer format: int32 message: type: string securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key ````