GET https://xquik.com/api/v1/x/users/{id}/followers
1 credit per result returned · All plans from $0.00012/credit · Supports guest paid reads
GET /api/v1/x/users/{id}/followers.
Omit
mode to get the fullest results. The response shape stays the same.
Pass next_cursor back unchanged as cursor. Keep the same endpoint, target,
query, and filters.after, limit, and
pageSize aliases also keep working. Billing still counts only returned rows.
Use mode=standard only to keep the legacy pagination.
A page can be empty or underfilled. Continue while has_next_page is true.
Stop only after the response reports has_next_page=false.
First-page requests do not support Idempotency-Key retries.
Repeating a cursorless request starts a separate extraction.
Results returned by that extraction incur their normal charges.
Save each response before requesting its next page.
A cursor sent again within 10 minutes returns the same page at no charge.
After 10 minutes, you cannot replay earlier or terminal responses.
If automatic coverage is busy, an initial request returns a standard data page.
Live coverage cursors remain atomic. A cursor sent again while its page loads
returns that page at no charge.
Other repeats return 409 coverage_cursor_unavailable with exact Retry-After
seconds. Wait, then send the same cursor again.
Repeated busy responses never authorize restarting with another cursor.
Expired, superseded, or identity-mismatched cursors return
410 coverage_cursor_gone. So does a cursor sent again after 10 minutes. The
response omits Retry-After. Restart without a cursor. Keep received results.
Deduplicate restarted results by id.
Malformed cursors return 400 invalid_coverage_cursor. Restart without them.
next_cursor in your
sync job. It can then resume from the last completed page.
Direct follower handoff
UseGET /api/v1/x/users/{id}/followers when a CRM, warehouse, audience, or
agent workflow needs follower rows. It returns them for one profile now. The
examples above write JSON Lines rows for imports or upserts. Each row is keyed
by x_user_id and holds its page’s cursor state.
Followers come newest first.Choose live API or saved export
Use this endpoint for current JSON pages in an app, queue, or agent. It fits when the caller can storenext_cursor and process users[] immediately. Use
follower_explorer for a
cost estimate, reusable extraction ID, stored result pages, or files. Its files
are CSV, JSON, or XLSX, ready after completion.
Automatic pageSize accepts 20 to 10,000. Standard mode accepts 20 to 200.
Paid calls can return fewer rows. users.length is the billable row count.
Zero affordable results return
402 insufficient_credits.
For high-volume follower pulls, deduplicate profiles by id. Continue through empty pages while the cursor advances. Stop with a partial-result status when next_cursor is missing or repeats.Build a Twitter follower tracker
An account monitor tracks followers for you, with no snapshot diff. Selectfollower.added and follower.removed. Each
event holds the follower’s profile, or its ID when X shows none. New followers
usually arrive within a minute. Losses take about 15 minutes, or up to 2 hours
above 5,000 followers.
follower.addedholdsfollowedAt, X’s time of the follow when X gives one.follower.removedholdsreasonwhen the cause is known.unfollowedmeans the follow ended.unavailablemeans X shows no account for it, as after a suspension.followKindmarks a returning follower asrefolloworreturn.profile.followers.changedreports follower count moves, at most once a minute.
users[].id, since usernames change. To track
without code, open the
Twitter unfollowers tracker.Which follower endpoint?
- Use
GET /api/v1/x/users/{id}/followersfor one account’s live follower page. - Use
follower_explorerwhen you need a saved job, CSV, JSON, or XLSX export. - Use
GET /api/v1/x/users/{id}/followingfor accounts the user follows. - Use
GET /api/v1/x/users/{id}/verified-followerswhen you only need verified followers. - Use Followers You Know for followers you share with another account.
- Use an account monitor for each new or lost follower.
Path parameters
Query parameters
User result filters
These filters apply before billing. Selective filters can return fewer rows.See user filters for every filter. Common ones areminFollowers, verifiedOnly, hasWebsite, hasEmail, bioContains, and locationContains.Choose fields
Headers
Response
200 OK
WithenrichProfiles=true, each row carries the full profile. The
x-xquik-profile-enrichment header then counts the rows that have it, as in
enriched=180; requested=200. A row without it keeps its list fields.400 Invalid user ID
{ "error": "invalid_user_id", "message": "Send a user ID, @username or profile URL, such as x.com/nasa." }401 Unauthenticated
Anonymous requests getWWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge.402 Payment required
Account keys get account options. Guest keys get guest top-up only. No checkout starts automatically. Confirm any payment action.502 X API unavailable
The read service returned an error. Retry after a short delay.429 Rate limit exceeded
You exceeded your tier rate limit. Wait for theRetry-After header before retrying.424 Dependency failed
The normalized v1 response contract can return 424 when the read service is unavailable.Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required." } - 402
{ "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "user_not_found", "message": "X user not found. Check the username." } - 409
{ "error": "coverage_cursor_unavailable", "message": "Cursor busy. Retry after the indicated delay." } - 410
{ "error": "coverage_cursor_gone", "message": "Cursor finished, expired, or superseded. Restart pagination without cursor." } - 424
{ "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 } - 502
{ "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." } - 503
{ "error": "x_api_unavailable", "message": "Maximum coverage is busy. Retry shortly." }