> ## 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.

# Twitter list followers API & profile export

> Retrieve Twitter List followers with usernames, bios, locations, profile images, verification, follower counts, following counts, and JSON cursor pages.

<Panel>
  <Tabs defaultTabIndex={0} sync={false}>
    <Tab title="200" id="response-x-list-followers-200">
      ```json theme={null}
      {
        "users": [],
        "has_next_page": false,
        "next_cursor": ""
      }
      ```
    </Tab>

    <Tab title="400" id="response-x-list-followers-400">
      ```json theme={null}
      {
        "error": "invalid_input",
        "message": "Invalid input. Check the request body."
      }
      ```
    </Tab>

    <Tab title="401" id="response-x-list-followers-401">
      ```json theme={null}
      {
        "error": "unauthenticated",
        "message": "Authentication required."
      }
      ```
    </Tab>

    <Tab title="402" id="response-x-list-followers-402">
      ```json theme={null}
      {
        "error": "insufficient_credits",
        "message": "Insufficient credits. Top up or subscribe to continue."
      }
      ```
    </Tab>

    <Tab title="404" id="response-x-list-followers-404">
      ```json theme={null}
      {
        "error": "not_found",
        "message": "Resource not found."
      }
      ```
    </Tab>

    <Tab title="409" id="response-x-list-followers-409">
      ```json theme={null}
      {
        "error": "coverage_cursor_unavailable",
        "message": "Cursor busy. Retry after the indicated delay."
      }
      ```
    </Tab>

    <Tab title="410" id="response-x-list-followers-410">
      ```json theme={null}
      {
        "error": "coverage_cursor_gone",
        "message": "Cursor finished, expired, or superseded. Restart pagination without cursor."
      }
      ```
    </Tab>

    <Tab title="424" id="response-x-list-followers-424">
      ```json theme={null}
      {
        "error": "x_api_unavailable",
        "message": "X data source temporarily unavailable. Try again later."
      }
      ```
    </Tab>

    <Tab title="429" id="response-x-list-followers-429">
      ```json theme={null}
      {
        "error": "rate_limit_exceeded",
        "message": "Too many requests. Try again later.",
        "retryAfter": 60
      }
      ```
    </Tab>

    <Tab title="502" id="response-x-list-followers-502">
      ```json theme={null}
      {
        "error": "x_api_unavailable",
        "message": "X data source temporarily unavailable. Try again later."
      }
      ```
    </Tab>

    <Tab title="503" id="response-x-list-followers-503">
      ```json theme={null}
      {
        "error": "x_api_unavailable",
        "message": "Maximum coverage is busy. Retry shortly."
      }
      ```
    </Tab>
  </Tabs>
</Panel>

<blockquote className="agent-llms-directive">
  For the complete documentation index, see <a href="/llms.txt">llms.txt</a>.
</blockquote>

This API returns one List's follower IDs, usernames, bios, locations,
verification, public counts, profile images, and cursors.

<Info>
  Omit `mode` for automatic maximum coverage. Xquik combines available views
  within a short request window. It keeps the existing response shape.
  Pass `next_cursor` back unchanged as `cursor`. Keep the same endpoint, target,
  query, and filters.
</Info>

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 force legacy single-view 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.
You cannot replay earlier or terminal responses after their cursors become unavailable.

If automatic coverage is busy, an initial request returns a standard data page.
Live coverage cursors remain atomic. Concurrent use returns
`409 coverage_cursor_unavailable` with exact `Retry-After` seconds. Wait, then
retry the same cursor once.
Repeated busy responses never authorize restarting with another cursor.

Finished, expired, superseded, or identity-mismatched cursors return
`410 coverage_cursor_gone`. 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.

## Twitter list followers questions

### What is a 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](https://help.x.com/en/using-x/x-lists)
for current List visibility and follow behavior.

### How do I find who follows a specific Twitter list?

Copy the numeric List ID from its X 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](https://docs.x.com/x-api/lists/get-list-followers) guide
uses different pagination field names.

### How do I export 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 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](/api-reference/x/list-members) for the curated
profile roster. That endpoint also reads profiles. It does not edit the List.

<Note>
  Requested result counts are upper bounds for paid authenticated calls. When remaining credits cannot cover the full page or ID list, Xquik returns fewer results. If zero paid results are affordable, it returns `402 insufficient_credits`.
</Note>

<Callout icon="coins" color="#5c3327">
  **1 credit per result returned** · [All plans](https://xquik.com/#pricing) from \$0.00012/credit
</Callout>

<CodeGroup>
  ```bash cURL theme={null}
  curl "https://xquik.com/api/v1/x/lists/1234567890/followers" \
    -H "x-api-key: xq_your_api_key_here" | jq
  ```

  ```javascript Node.js theme={null}
  const listId = "1234567890";
  const response = await fetch(`https://xquik.com/api/v1/x/lists/${listId}/followers`, {
    headers: { "x-api-key": "xq_your_api_key_here" },
  });
  const data = await response.json();
  const followerRows = data.users.map((user) => ({
    list_id: listId,
    follower_id: user.id,
    username: user.username,
    display_name: user.name,
    bio: user.description ?? null,
    follower_count: user.followers ?? null,
    following_count: user.following ?? null,
    verified: user.verified ?? false,
    profile_image_url: user.profilePicture ?? null,
  }));
  const nextCursor = data.has_next_page ? data.next_cursor : null;
  ```

  ```python Python theme={null}
  import requests

  list_id = "1234567890"
  response = requests.get(
      f"https://xquik.com/api/v1/x/lists/{list_id}/followers",
      headers={"x-api-key": "xq_your_api_key_here"},
  )
  data = response.json()
  follower_rows = [
      {
          "list_id": list_id,
          "follower_id": user["id"],
          "username": user["username"],
          "display_name": user["name"],
          "bio": user.get("description"),
          "follower_count": user.get("followers"),
          "following_count": user.get("following"),
          "verified": user.get("verified", False),
          "profile_image_url": user.get("profilePicture"),
      }
      for user in data["users"]
  ]
  next_cursor = data["next_cursor"] if data["has_next_page"] else None
  ```
</CodeGroup>

## 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`](/api-reference/extractions/create) 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`.

<CardGroup cols={2}>
  <Card title="List follower audience" icon="user-plus">
    Page accounts that follow the list. Store the row shape above for CRM,
    warehouse, and audience imports.
  </Card>

  <Card title="Next page" icon="arrow-right">
    Store `has_next_page` and `next_cursor`. Only request another page when
    `has_next_page` is true.
  </Card>

  <Card title="Default page" icon="rows-3">
    Direct calls use the default paid page size. The returned
    `users.length` is the row count for this page.
  </Card>

  <Card title="Saved export" icon="file-spreadsheet">
    Use `list_follower_explorer` when the workflow needs a saved job with
    CSV, JSON, or XLSX output.
  </Card>
</CardGroup>

## Measure 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 or prove interest in every List topic.

## Path parameters

<ParamField path="id" type="string" required>
  List ID (numeric string).
</ParamField>

## Query parameters

<ParamField query="cursor" type="string">
  Pass `next_cursor` back unchanged. Xquik cursors resume automatic coverage.
  Existing unprefixed cursors keep legacy behavior.
</ParamField>

<ParamField query="mode" type="string">
  Omit `mode` for automatic maximum coverage. Use `standard` for legacy
  pagination. Use `coverage` for one diagnostic response without cursors.
</ParamField>

<ParamField query="after" type="string">
  Legacy cursor alias for `cursor`. When both are present, `cursor` wins.
</ParamField>

<ParamField query="pageSize" type="integer">
  Automatic pages accept `1-300`. Standard pages accept `1-200`. Default: `200`.
</ParamField>

## Which list endpoint?

<CardGroup cols={2}>
  <Card title="List followers" icon="user-plus">
    Use `GET /x/lists/{id}/followers` for accounts that follow the list.
  </Card>

  <Card title="List members" icon="users">
    Use [`GET /x/lists/{id}/members`](/api-reference/x/list-members) for
    accounts the list owner added to the list.
  </Card>

  <Card title="List tweets" icon="message-square-text">
    Use [`GET /x/lists/{id}/tweets`](/api-reference/x/list-tweets) for tweets
    from accounts in the list.
  </Card>

  <Card title="Bulk list jobs" icon="file-spreadsheet">
    Use [`Create extraction`](/api-reference/extractions/create) with
    `list_follower_explorer`, `list_member_extractor`, or `list_post_extractor`
    when the workflow needs a saved export.
  </Card>
</CardGroup>

### User result filters

These filters apply before billing. Selective filters can return fewer rows.

<ParamField query="minFollowers" type="integer">
  Require this minimum follower count. Filtering happens before billing.
</ParamField>

<ParamField query="maxFollowers" type="integer">
  Allow this maximum follower count. Missing counts pass this filter.
</ParamField>

<ParamField query="minFollowing" type="integer">
  Require this minimum following count.
</ParamField>

<ParamField query="maxFollowing" type="integer">
  Allow this maximum following count. Missing counts pass this filter.
</ParamField>

<ParamField query="minStatuses" type="integer">
  Require this minimum post count.
</ParamField>

<ParamField query="maxStatuses" type="integer">
  Allow this maximum post count. Missing counts pass this filter.
</ParamField>

<ParamField query="minAccountAgeDays" type="integer">
  Require this minimum account age in days.
</ParamField>

<ParamField query="verifiedOnly" type="boolean">
  When `true`, only return verified profiles.
</ParamField>

<ParamField query="verifiedType" type="string">
  Match the exact verification type.
</ParamField>

<ParamField query="hasWebsite" type="boolean">
  When `true`, require a profile website.
</ParamField>

<ParamField query="hasLocation" type="boolean">
  When `true`, require a profile location.
</ParamField>

<ParamField query="bioContains" type="string">
  Require every comma-separated or line-separated bio term.
</ParamField>

<ParamField query="locationContains" type="string">
  Require this text in the profile location.
</ParamField>

<ParamField query="usernameContains" type="string">
  Require this text in the username.
</ParamField>

## Headers

<ParamField header="x-api-key" type="string">
  Full account key. Sessions and OAuth also work.
</ParamField>

<ParamField header="Authorization" type="string">
  `Bearer xq_your_guest_key_here` for `paid_reads`.
</ParamField>

## Response

### 200 OK

<ResponseField name="users" type="object[]">
  Array of list followers.
  **User object fields.**

  <ResponseField name="id" type="string">
    User ID.
  </ResponseField>

  <ResponseField name="username" type="string">
    X username.
  </ResponseField>

  <ResponseField name="name" type="string">
    Display name.
  </ResponseField>

  <ResponseField name="description" type="string">
    Contains the profile bio.
  </ResponseField>

  <ResponseField name="followers" type="number">
    Shows how many accounts follow this profile.
  </ResponseField>

  <ResponseField name="following" type="number">
    Shows how many accounts this profile follows.
  </ResponseField>

  <ResponseField name="verified" type="boolean">
    Shows if X marks this profile as verified.
  </ResponseField>

  <ResponseField name="profilePicture" type="string">
    Links to the profile image.
  </ResponseField>

  <ResponseField name="location" type="string">
    Shows the location written on the profile.
  </ResponseField>

  <ResponseField name="createdAt" type="string">
    Shows when the account began, in ISO 8601 format.
  </ResponseField>

  <ResponseField name="statusesCount" type="number">
    Shows the post count if X returns it.
  </ResponseField>

  <ResponseField name="coverPicture" type="string">
    Links to the cover image if X returns it.
  </ResponseField>

  <ResponseField name="mediaCount" type="number">
    Shows the media post count if X returns it.
  </ResponseField>

  <ResponseField name="url" type="string">
    Website URL from profile. Omitted if empty.
  </ResponseField>

  <ResponseField name="favouritesCount" type="number">
    Shows how many posts this account liked if X returns it.
  </ResponseField>

  <ResponseField name="hasCustomTimelines" type="boolean">
    Shows custom timelines if X returns this field.
  </ResponseField>

  <ResponseField name="isTranslator" type="boolean">
    Shows X translator status if X returns it.
  </ResponseField>

  <ResponseField name="withheldInCountries" type="string[]">
    Lists country codes where X withholds this account. Omitted if empty.
  </ResponseField>

  <ResponseField name="possiblySensitive" type="boolean">
    Shows if X marks the account as sensitive. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="pinnedTweetIds" type="string[]">
    Lists pinned Tweet IDs. Omitted if none.
  </ResponseField>

  <ResponseField name="isAutomated" type="boolean">
    Shows if X marks this account as automated. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="automatedBy" type="string">
    Names the operator. Omitted when the account is not automated.
  </ResponseField>

  <ResponseField name="unavailable" type="boolean">
    Shows if X could not load the account. Omitted when X loads it.
  </ResponseField>

  <ResponseField name="unavailableReason" type="string">
    Explains why X could not load the account. Omitted when X loads it.
  </ResponseField>

  <ResponseField name="verifiedType" type="string">
    Shows `Business` or `Government` status. Omitted for blue checks or unverified profiles.
  </ResponseField>

  <ResponseField name="profile_bio" type="object">
    Adds the structured bio and its tags. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="isBlueVerified" type="boolean">
    Shows if X Premium verifies the account. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="isVerified" type="boolean">
    Shows the normalized verified state. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="profileBannerUrl" type="string">
    Links to the profile banner. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="protected" type="boolean">
    Shows if the account protects its posts. Omitted if X does not send it.
  </ResponseField>

  <ResponseField name="communityRole" type="string">
    Shows a community role only in community results.
  </ResponseField>
</ResponseField>

<ResponseField name="has_next_page" type="boolean">Shows if another page exists.</ResponseField>
<ResponseField name="next_cursor" type="string">Gives the next cursor. Pass it as the `cursor` query value.</ResponseField>

```json theme={null}
{
  "users": [
    {
      "id": "987654321",
      "username": "username",
      "name": "Xquik",
      "followers": 10000,
      "verified": true
    }
  ],
  "has_next_page": true,
  "next_cursor": "DAACCgACGE..."
}
```

### 400 Invalid list ID

```json theme={null}
{ "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.

```json theme={null}
{ "error": "unauthenticated" }
```

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

```json theme={null}
{ "error": "not_found" }
```

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

### 502 X API unavailable

```json theme={null}
{ "error": "x_api_unavailable" }
```

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

### 429 Rate limit exceeded

```json theme={null}
{ "error": "rate_limit_exceeded", "retryAfter": 60 }
```

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

### 424 Dependency failed

```json theme={null}
{ "error": "x_api_unavailable" }
```

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

<Note>
  **Related.** [List Members](/api-reference/x/list-members) · [List Tweets](/api-reference/x/list-tweets)
</Note>

<div className="related-api-links">
  <Accordion title="Related follower, list & community APIs" icon="link">
    * Profiles: [Search users](/api-reference/x/search-users) · [Search autocomplete](/api-reference/x/search-autocomplete) · [Get user](/api-reference/x/twitter-profile-lookup) · [Batch users](/api-reference/x/batch-users)
    * Followers: [Followers](/api-reference/x/followers) · [Following](/api-reference/x/following) · [Follower IDs](/api-reference/x/follower-ids) · [Following IDs](/api-reference/x/following-ids) · [Creator subscriptions](/api-reference/x/user-subscriptions) · [Affiliates](/api-reference/x/user-affiliates) · [Similar accounts](/api-reference/x/user-similar) · [Verified followers](/api-reference/x/verified-followers) · [Followers you know](/api-reference/x/followers-you-know) · [Check follower](/api-reference/x/check-follower)
    * Lists: [Search lists](/api-reference/x/search-lists) · [User lists](/api-reference/x/user-lists) · [List memberships](/api-reference/x/user-list-memberships) · [List members](/api-reference/x/list-members) · [List followers](/api-reference/x/list-followers)
    * Communities: [Find](/api-reference/x/community-find) · [Popular](/api-reference/x/community-popular) · [Topics](/api-reference/x/community-topics) · [Suggested](/api-reference/x/community-suggested) · [Details](/api-reference/x/community-info) · [Members](/api-reference/x/community-members) · [Moderators](/api-reference/x/community-moderators) · [Timeline](/api-reference/x/community-tweets) · [Media](/api-reference/x/community-media) · [Keyword search](/api-reference/x/community-search)
  </Accordion>
</div>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.