Skip to main content
GET https://xquik.com/api/v1/x/lists/{id}/followers This API returns one List’s follower IDs, usernames, bios, and locations. It also returns verification, public counts, profile images, and cursors.
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.
Existing unprefixed cursors keep their legacy behavior. 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.

X (Twitter) list followers questions

What is an X (Twitter) list follower?

A List follower subscribes to one List. A List member is an account selected by the List owner. An account follower follows one profile instead. X says anyone can follow a public List. Only its owner can access a private List. Read X’s official Lists guide for current List visibility and follow behavior.

How do I find who follows a specific X (Twitter) list?

Copy the numeric List ID from its X (Twitter) URL. Request the first page without a cursor. Store every returned user row before requesting another page. Xquik returns has_next_page and next_cursor. Continue only when has_next_page is true. Pass next_cursor unchanged as the next cursor. X also documents a List follower route. Its official Get List followers guide uses different pagination field names.

How do I export X (Twitter) list followers?

The direct endpoint returns JSON pages with named fields. Convert each profile into one row. Store the List ID, user ID, username, bio, counts, and request time. Use list_follower_explorer for a saved X (Twitter) List follower export. The job can produce CSV, JSON, or XLSX files without custom spreadsheet code.

What can I check in each Twitter profile?

Check user IDs, usernames, bios, and public location text. Check when each account began, its verified status, and its public counts. Check automated, protected, and unavailable flags only when the response includes them. These fields do not show age, gender, income, identity, consent, or sentiment. A profile location does not prove where someone lives.

Can this API add, remove, or buy list followers?

No. This read endpoint cannot follow a List or remove a List follower. It cannot create Lists, manage List members, publish posts, or buy followers. Use the List Members endpoint for the curated profile roster. That endpoint also reads profiles. It does not edit the List.
Requested result counts are upper bounds for paid authenticated calls. Remaining credits may not cover the full page or ID list. If so, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per result returned · All plans from $0.00012/credit

Direct list follower handoff

GET /x/lists/{id}/followers examples build one row per List follower. Send saved rows to a CRM, warehouse, audience tool, or agent. Use list_follower_explorer for a saved job and CSV, JSON, or XLSX export. Store list_id, follower_id, username, and display_name. Keep profile counts, verified state, has_next_page, and next_cursor.

List follower audience

Page accounts that follow the list. Store the row shape above for CRM, warehouse, and audience imports.

Next page

Store has_next_page and next_cursor. Only request another page when has_next_page is true.

Default page

Direct calls use the default paid page size. The returned users.length is the row count for this page.

Saved export

Use list_follower_explorer when the workflow needs a saved job. The job has CSV, JSON, or XLSX output.

Measure X (Twitter) list follower profiles

Use List followers for profiles that chose to follow one List. Keep the List ID with every profile. This keeps follower rows apart from List member rows. Save these fields.
  • User ID, username, and profile name.
  • Bio, location, and verified state.
  • Follower and following counts.
  • List ID, cursor, and collection time.
Compare List follower snapshots by user ID. Record new and missing IDs on separate lines. A new username does not mean a new follower. Use list members when you need the list owner’s curated roster. Use account followers when you need the audience of one profile. Each endpoint returns a different relationship. For outreach review, keep source list context. Never infer consent or contact permission from a public follow relationship.

Track list audience changes

Finish both follower snapshots before finding added or missing IDs. Record the List ID, request time, page count, and final row count. Use follower user IDs as stable match keys. Keep usernames as labels. Mark stopped or credit-limited jobs as partial. A snapshot diff shows the List followers seen in each run. It does not show changes to the List’s member roster. Report newly observed follower IDs separately from missing IDs. Keep both snapshot completion states beside the comparison. Use snapshot differences to review the audience only. A public follow does not grant outreach rights. It also does not prove interest in every List topic.

Path parameters

Query parameters

Choose fields

Which list endpoint?

List followers

Use GET /x/lists/{id}/followers for accounts that follow the list.

List members

Use GET /x/lists/{id}/members for accounts the list owner added to the list.

List tweets

Use GET /x/lists/{id}/tweets for tweets from accounts in the list.

Bulk list jobs

Use Create extraction with list_follower_explorer, list_member_extractor, or list_post_extractor when the workflow needs a saved export.

User result filters

These filters apply before billing. Selective filters can return fewer rows.See user filters for every filter. Common ones are minFollowers, verifiedOnly, hasWebsite, hasEmail, bioContains, and locationContains.

Headers

Response

200 OK

400 Invalid list ID

{ "error": "invalid_list_id", "message": "List ID required" } The list ID path parameter is empty.

401 Unauthenticated

Anonymous requests get WWW-Authenticate: Bearer and a guest wallet checkout action. This is not a Payment challenge. Missing or invalid API key.

402 Payment required

Account keys get account options. Guest keys get guest top-up only. No checkout starts automatically. Confirm any payment action.

404 List not found

Xquik could not resolve the list. Check the list ID.

502 X API unavailable

The read service returned an error. Retry after a short delay.

429 Rate limit exceeded

You exceeded your tier’s rate limit. Wait for the Retry-After header before retrying.

424 Dependency failed

The v1 response can return 424 when the read service fails.

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": "not_found", "message": "Resource not found." }
  • 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." }