Skip to main content
GET https://xquik.com/api/v1/x/lists/{id}/members This route reads one X List. It returns the profiles the List owner added. Keep user IDs, usernames, bios, verification, profile images, and public counts.
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 members questions

What is an X (Twitter) list member?

A List member is an account selected by the List owner. Membership creates the List’s curated timeline. It does not mean the account follows that List. An account follower follows one profile instead. X explains these roles in its official Lists guide.

How do I view members of an X (Twitter) list?

Copy the numeric List ID from its X (Twitter) URL. Request the first page without a cursor. Store every returned profile before requesting another page. Continue only when has_next_page is true. Pass next_cursor unchanged as cursor. X also documents a Get List members route. Its response and pagination fields differ from Xquik’s fields.

How do I export X (Twitter) list members?

The direct endpoint returns JSON pages. Convert each profile into one export row. Store the List ID, member ID, username, bio, counts, and collection time. Follow every cursor before treating the export as complete. Use list_member_extractor for a saved job. It can produce CSV, JSON, or XLSX files without custom spreadsheet code.

Which profile fields can I analyze?

Analyze user IDs, usernames, display names, bios, and public location text. Compare follower counts, following counts, verification, and account dates. Use public counts to sort a roster for manual review. Do not call a high count “influence” without a clear method. This endpoint does not calculate reach, engagement, demographics, sentiment, or audience quality.

How do I compare list member snapshots?

Finish both snapshots before comparing their member IDs. Added IDs indicate newly observed members. Missing IDs indicate newly unobserved members. Record both snapshot times and completion states. A renamed username is not a new member. Never report removals from an incomplete later snapshot.

Can I export members from a private X (Twitter) list?

Private Lists return only what X makes public. Never assume a private List is readable. A 404 means the List is unavailable or the List ID is wrong. Do not promise access to private Lists. Public profile fields also do not grant outreach consent.

Can this endpoint add or remove list members?

No. This GET endpoint only reads the current roster. It cannot create Lists, add members, remove members, follow Lists, or publish tweets. Use X’s supported write tools for owner-authorized changes. Xquik does not expose those actions through this endpoint.

How do I find active members or recent tweets?

This response describes profiles, not recent activity. Retrieve List Tweets for posts from the current List timeline. Analyze tweets separately from List membership. A profile count does not prove recent activity. One active account can publish many posts while remaining one List member.
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 member handoff

GET /x/lists/{id}/members examples create one row per List member. Send saved rows to a CRM, warehouse, audience tool, or agent. Use list_member_extractor for a saved job. That job supports CSV, JSON, or XLSX file export. Store list_id, member_id, username, and display_name. Keep profile counts, verification, has_next_page, and next_cursor.

Member roster

Page accounts the list owner curated as members. Use 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.

Page size

Automatic pages accept 1-10000. Standard accepts 1-200. The returned users.length is the row count for the page.

Saved export

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

Export a curated list roster

Use List members for profiles selected by one List owner. Keep the List ID on every row. Also keep the collection time and snapshot status. These list-member columns are useful.
  • User ID, username, and profile name.
  • Biography, location, and verification state.
  • Follower and following counts.
  • List ID and collection timestamp.
Compare snapshots by user ID. Profile owners can rename their usernames. List membership reflects curation, not audience interest. Use List followers for profiles that follow the List. Use account followers for one profile’s audience. For CRM imports, deduplicate by List ID and user ID. The same profile can then appear under several Lists.

Track list curation changes

Create complete snapshots at consistent intervals. Mark added user IDs as newly observed members. Mark missing IDs only after a complete later snapshot. Keep the list name and owner in your snapshot metadata. The endpoint path uses the list ID. Reviewers often recognize the readable name. Use snapshot differences to review curation decisions. Do not call them follower growth. The List owner controls membership. Create one change row for each added or removed user ID. Include the earlier and later snapshot times. Keep the current username only as a display label. Send uncertain comparisons to review. Never publish incomplete comparisons.

Path parameters

Query parameters

Choose fields

Which list endpoint?

List members

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

List followers

Use GET /x/lists/{id}/followers for accounts that follow 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_member_extractor, list_follower_explorer, 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.

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." }