Skip to main content
GET
/
x
/
users
/
{id}
/
followers
Get followers
curl --request GET \
  --url https://xquik.com/api/v1/x/users/{id}/followers \
  --header 'x-api-key: <api-key>'

Documentation Index

Fetch the complete documentation index at: https://docs.xquik.com/llms.txt

Use this file to discover all available pages before exploring further.

1 credit per result returned · All plans from $0.00012/credit · Accepts MPP
Get followers returns follower profiles for one X account by username or numeric user ID. It is also useful as a Follower Export API, X followers API, or Twitter followers API. The canonical endpoint remains GET /api/v1/x/users/{id}/followers.
# Username follower page
curl "https://xquik.com/api/v1/x/users/xquikcom/followers?pageSize=200" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

# Numeric user ID follower page
curl "https://xquik.com/api/v1/x/users/44196397/followers?pageSize=200" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq

# Resume with next_cursor from the previous page
curl -G "https://xquik.com/api/v1/x/users/xquikcom/followers" \
  --data-urlencode "cursor=DAACCgACGE..." \
  --data-urlencode "pageSize=200" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
The Node.js and Python snippets write JSON Lines import rows instead of raw follower pages. Persist each mapped row and the latest next_cursor in your sync job so it can resume from the last completed page.

​
Direct follower handoff

Use GET /api/v1/x/users/{id}/followers when a CRM, warehouse, audience, or agent workflow needs follower rows for one profile now. The examples above write JSON Lines rows with source_user_id_or_username, x_user_id, x_username, display_name, profile enrichment, segmentation fields, page_index, page_cursor, next_cursor, and has_next_page for imports or upserts. Use follower_explorer when you need an estimated job, saved extraction, or CSV/JSON/XLSX file export.

​
Choose live API or saved export

Use this endpoint for current JSON pages when an app, queue, or agent can store next_cursor and process users[] immediately. Use follower_explorer when the job needs a cost estimate, reusable extraction ID, stored result pages, or CSV/JSON/XLSX files after completion.

Live page

Call GET /x/users/{id}/followers with pageSize and cursor for low-latency imports, enrichment, queues, or agent handoffs.

Saved export

Run follower_explorer when operators need estimates, job status, paginated saved rows, or file downloads.

Follower rows

Store users[] as the follower profile rows returned on this page.

Stable upserts

Store users[].id as x_user_id for CRM, warehouse, audience, and agent dedupe.

Readable labels

Store users[].username and users[].name for handles, labels, enrichment, and dedupe.

Profile enrichment

Store users[].description, location, and url when returned. Empty profile fields are omitted.

Segmentation inputs

Store users[].followers, users[].following, verified, and verifiedType for filters and scoring.

Profile media

Store users[].profilePicture and coverPicture for enrichment, review queues, or profile previews.

Next page

Store has_next_page and next_cursor; pass next_cursor back as cursor only when has_next_page is true.

Credit-limited pages

Use users.length, not the requested pageSize, for row counts and budget checks. Low balances can return fewer rows.
pageSize from 20 to 200 is an upper bound. Paid authenticated calls can return fewer rows when the remaining credit balance is lower than the requested page size. Treat the returned users.length as the billable row count for that page. A balance that cannot afford any result returns 402 insufficient_credits. For MPP callers, this endpoint is billed as a session at USD 0.00015 per user returned.

​
Which follower endpoint?

  • Use GET /api/v1/x/users/{id}/followers for one account’s live follower page.
  • Use follower_explorer when you need a saved job, CSV, JSON, or XLSX export.
  • Use GET /api/v1/x/users/{id}/following for accounts the user follows.
  • Use GET /api/v1/x/users/{id}/verified-followers when you only need verified followers.

​
Path parameters

​
id
string
required
Username or numeric user ID. For example, use xquikcom or 44196397.

​
Query parameters

​
cursor
string
Opaque pagination cursor from next_cursor in the previous response. Omit for the first page.
​
after
string
Legacy cursor alias for cursor. When both are present, cursor wins.
​
pageSize
number
Results per page. Range: 20-200. Default: 200. Remaining credits can reduce the returned row count.
​
limit
number
Legacy page size alias. Use pageSize; when both are present, pageSize wins.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
users
object[]
Array of follower profiles.
​
has_next_page
boolean
Whether more results are available.
​
next_cursor
string
Cursor for the next page.
{
  "users": [
    {
      "id": "987654321",
      "username": "xquikcom",
      "name": "Xquik",
      "followers": 10000,
      "following": 500,
      "verified": true,
      "profilePicture": "https://pbs.twimg.com/profile_images/xquik/photo.jpg",
      "description": "All-in-one X automation platform"
    }
  ],
  "has_next_page": true,
  "next_cursor": "DAACCgACGE..."
}
Related: Follower Export CRM Workflow for saved CSV, JSON, or XLSX files for imports or upserts, Following, Verified Followers, and Followers You Know.
Last modified on May 24, 2026