> ## 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 verified followers API & profile export

> Retrieve verified X followers by username or numeric user ID with cursor pagination for CRM, scoring, enrichment, and agent workflows. 1 credit per result.

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

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

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

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

    <Tab title="403" id="response-x-verified-followers-403">
      ```json theme={null}
      {
        "error": "x_account_protected",
        "message": "This account's verified follower list is private. Try a public account."
      }
      ```
    </Tab>

    <Tab title="404" id="response-x-verified-followers-404">
      ```json theme={null}
      {
        "error": "user_not_found",
        "message": "X user not found. Check the username."
      }
      ```
    </Tab>

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

    <Tab title="410" id="response-x-verified-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-verified-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-verified-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-verified-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-verified-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>

Retrieve verified profiles that follow one X account. Store stable user IDs,
handles, verification types, counts, and pagination cursors.

<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 · Supports [guest paid reads](/guides/guest-wallets)
</Callout>

Get verified followers returns verified profiles that follow one X account by
username or numeric user ID. The
endpoint is `GET /api/v1/x/users/{id}/verified-followers`.

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

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

  ```bash Numeric user ID theme={null}
  curl "https://xquik.com/api/v1/x/users/44196397/verified-followers" \
    -H "x-api-key: xq_your_api_key_here" | jq
  ```

  ```javascript Node.js theme={null}
  const userId = "44196397";
  const response = await fetch(`https://xquik.com/api/v1/x/users/${userId}/verified-followers`, {
    headers: { "x-api-key": "xq_your_api_key_here" },
  });
  const data = await response.json();
  const verifiedRows = data.users.map((user) => ({
    source_user_id: userId,
    x_user_id: user.id,
    username: user.username,
    display_name: user.name,
    verified_type: user.verifiedType ?? "standard",
    follower_count: user.followers ?? null,
    following_count: user.following ?? null,
    profile_image_url: user.profilePicture ?? null,
  }));
  const nextCursor = data.has_next_page ? data.next_cursor : null;
  const checkpoint = { source_user_id: userId, next_cursor: nextCursor };

  for (const row of verifiedRows) {
    process.stdout.write(`${JSON.stringify(row)}\n`);
  }
  process.stdout.write(`${JSON.stringify(checkpoint)}\n`);
  ```

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

  user_id = "44196397"
  response = requests.get(
      f"https://xquik.com/api/v1/x/users/{user_id}/verified-followers",
      headers={"x-api-key": "xq_your_api_key_here"},
  )
  data = response.json()
  verified_rows = [
      {
          "source_user_id": user_id,
          "x_user_id": user["id"],
          "username": user["username"],
          "display_name": user["name"],
          "verified_type": user.get("verifiedType", "standard"),
          "follower_count": user.get("followers"),
          "following_count": user.get("following"),
          "profile_image_url": user.get("profilePicture"),
      }
      for user in data["users"]
  ]
  next_cursor = data["next_cursor"] if data["has_next_page"] else None
  checkpoint = {"source_user_id": user_id, "next_cursor": next_cursor}

  for row in verified_rows:
      print(json.dumps(row))
  print(json.dumps(checkpoint))
  ```
</CodeGroup>

The Node.js and Python snippets build verified follower rows. They do not
print the full response page. Store `verifiedRows` or `verified_rows` with
the checkpoint. A worker can then resume pagination with `next_cursor` without
duplicating imported profiles.

## Direct verified followers handoff

Use `GET /x/users/{id}/verified-followers` when a CRM, warehouse, scoring, enrichment, or agent workflow needs one JSON page of verified followers now. The endpoint accepts a username or numeric user ID. It returns verified follower profile rows with cursor fields. Use [`verified_follower_explorer`](/api-reference/extractions/create) when you need an estimated job, saved extraction, or CSV, JSON, or XLSX file export.

<CardGroup cols={2}>
  <Card title="Verified rows" icon="badge-check">
    Store `users[]` as the verified follower profile rows returned on this page.
  </Card>

  <Card title="Stable upserts" icon="key-round">
    Store `users[].id` as `x_user_id` for CRM, warehouse, scoring, and agent deduplication.
  </Card>

  <Card title="Readable labels" icon="badge">
    Store `users[].username` and `users[].name` for handles, labels, enrichment, and review queues.
  </Card>

  <Card title="Verification signals" icon="shield-check">
    Store `users[].verified` and `verifiedType` to segment standard, business, and government accounts.
  </Card>

  <Card title="Audience signals" icon="chart-no-axes-combined">
    Store `users[].followers`, `users[].following`, and `statusesCount` for scoring and prioritization.
  </Card>

  <Card title="Profile enrichment" icon="file-text">
    Store `users[].description`, `location`, `url`, `profilePicture`, and `coverPicture` when returned.
  </Card>

  <Card title="Next page" icon="arrow-right">
    Store `has_next_page` and `next_cursor`, then pass `next_cursor` back as `cursor` only when `has_next_page` is true.
  </Card>
</CardGroup>

Direct verified followers cost 1 credit per user returned. Low credit balances can return fewer users than a full page. Zero affordable results return `402 insufficient_credits`.

A protected account returns 403 `x_account_protected`. Xquik charges nothing.

## Review verified followers separately

Use this route when the verification filter is part of the question. Keep the
source account ID with every returned profile.

Verified follower rows can support account research, partner review, or
audience segmentation. Verification does not prove relevance or endorsement.
Apply another review step before outreach or ranking.

## Build a verified follower directory

Start with one source account ID or username. Resolve and store its stable user
ID. Keep that source ID on every verified follower row.

Store follower user ID, username, profile name, biography, location, and
profile image when returned. Keep `verified` and `verifiedType` as separate
fields. Add follower count, following count, and collection time.

Use verification type for a documented segment. Do not translate it into
authority, relevance, identity quality, or endorsement. Add those judgments
only through your own reviewed process.

Use stable follower IDs for CRM upserts. Usernames, names, biographies,
images, verification, and counts can change. Overwrite them on each import. Keep
rejected import rows for review.

## Validate verified follower export completeness

Deduplicate resumed pages by source account ID and follower user ID. Keep the
newest complete profile fields. Keep the earliest collection evidence when
an audit needs it.

Record page count, unique row count, first cursor, last cursor, and completion
time. Mark result caps, low credits, failed pages, and interrupted downloads.
Never call those runs complete.

Compare the exported row count with the saved extraction result when using a
job. Investigate duplicate user IDs, rejected rows, and parsing errors. Check
incomplete downloads before loading a warehouse.

## Path parameters

<ParamField path="id" type="string" required>
  User ID, username with or without `@`, or URL-encoded profile URL, such as
  `x.com/nasa`. See [path IDs](/api-reference/overview#path-ids).
</ParamField>

## Query parameters

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

<ParamField query="mode" type="string">
  Optional compatibility override. Omit it for automatic maximum coverage.
  Use `standard` for legacy single-view pagination. Use `coverage` for a
  one-shot diagnostic response without cursor pagination.
</ParamField>

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

<ParamField query="pageSize" type="number">
  Automatic pages accept `20` through `300`. Standard pages accept `20` through
  `200`. The default is `200`. Sources can return fewer profiles.
</ParamField>

<ParamField query="limit" type="number">
  With `mode=coverage`, set a one-shot cap from `1` through `10000`.
  Otherwise, this is a legacy page size alias. `pageSize` wins.
</ParamField>

<ParamField query="enrichProfiles" type="boolean" default="false">
  Set `true` to add each row's full profile, as `GET /x/users/{id}` returns it.
  Pages take several seconds longer. The price per row stays the same. Later
  pages can leave it out, & `next_cursor` still works.
</ParamField>

## Which verified follower endpoint?

<CardGroup cols={2}>
  <Card title="Verified followers" icon="badge-check">
    Use `GET /x/users/{id}/verified-followers` for verified accounts that follow
    one profile.
  </Card>

  <Card title="All followers" icon="users-round">
    Use [`GET /x/users/{id}/followers`](/api-reference/x/followers) when you need
    verified and unverified followers.
  </Card>

  <Card title="Following list" icon="user-plus">
    Use [`GET /x/users/{id}/following`](/api-reference/x/following) for accounts
    the profile follows.
  </Card>

  <Card title="Saved exports" icon="file-spreadsheet">
    Use [`verified_follower_explorer`](/api-reference/extractions/create) for a
    saved verified follower extraction with CSV, JSON, or XLSX download handoff.
  </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

With `enrichProfiles=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.

<ResponseField name="users" type="object[]">
  Array of verified follower profiles.
  **User object fields.**

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

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

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

  <ResponseField name="description" type="string">
    Profile bio. Omitted if empty.
  </ResponseField>

  <ResponseField name="followers" type="number">
    Follower count.
  </ResponseField>

  <ResponseField name="following" type="number">
    Following count.
  </ResponseField>

  <ResponseField name="verified" type="boolean">
    Whether the user is verified. Always true for this endpoint.
  </ResponseField>

  <ResponseField name="verifiedType" type="string">
    Verification type (for example `Business`, `Government`). Omitted for standard blue check.
  </ResponseField>

  <ResponseField name="profilePicture" type="string">
    Profile picture URL.
  </ResponseField>

  <ResponseField name="location" type="string">
    Profile location. Omitted if empty.
  </ResponseField>

  <ResponseField name="accountBasedIn" type="object | null">
    Country or region X shows for the account, with `value`, `level` & `observedAt`. X infers it from
    account access. It states no nationality or exact location. `null` when X shows none. Present with
    `enrichProfiles=true`, unless X withholds it.
  </ResponseField>

  <ResponseField name="accountBasedInUnavailable" type="boolean">
    `true` when X withheld `accountBasedIn` from this row. Retry later to get it. Omitted otherwise.
  </ResponseField>

  <ResponseField name="createdAt" type="string">
    ISO 8601 account creation timestamp.
  </ResponseField>

  <ResponseField name="statusesCount" type="number">
    Total number of tweets posted. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="coverPicture" type="string">
    Cover or banner image URL. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="mediaCount" type="number">
    Total number of media tweets posted. Omitted if unavailable.
  </ResponseField>

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

  <ResponseField name="favouritesCount" type="number">
    Total number of tweets liked. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="hasCustomTimelines" type="boolean">
    Whether the user has custom timelines. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="isTranslator" type="boolean">
    Whether the user is an X translator. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="withheldInCountries" type="string[]">
    Country codes where the account is withheld. Omitted if empty.
  </ResponseField>

  <ResponseField name="possiblySensitive" type="boolean">
    Whether X flags the account as possibly sensitive. Omitted if unavailable.
  </ResponseField>

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

  <ResponseField name="isAutomated" type="boolean">
    Whether X marks the account as automated. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="automatedBy" type="string">
    Username of the account operator if automated. Omitted if not automated.
  </ResponseField>

  <ResponseField name="unavailable" type="boolean">
    Whether the account is unavailable. Omitted if available.
  </ResponseField>

  <ResponseField name="unavailableReason" type="string">
    Reason the account is unavailable. Omitted if available.
  </ResponseField>

  <ResponseField name="profile_bio" type="object">
    Structured profile bio with entity annotations. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="isBlueVerified" type="boolean">
    Whether the account has X Premium verification. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="isVerified" type="boolean">
    Normalized verification status. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="profileBannerUrl" type="string">
    Profile banner URL. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="protected" type="boolean">
    Whether the account protects its posts. Omitted if unavailable.
  </ResponseField>

  <ResponseField name="communityRole" type="string">
    Role within the requested community context. Omitted outside community results.
  </ResponseField>
</ResponseField>

<ResponseField name="has_next_page" type="boolean">Whether more results are available.</ResponseField>
<ResponseField name="next_cursor" type="string">Cursor for the next page.</ResponseField>

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

### 400 Invalid user ID

```json theme={null}
{
  "error": "invalid_user_id",
  "message": "Send a user ID, @username or profile URL, such as x.com/nasa."
}
```

### 404 User not found

```json theme={null}
{ "error": "user_not_found", "message": "X user not found. Check the username." }
```

### 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" }
```

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

```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 rate limit. Wait for the `Retry-After` header before retrying.

### 424 Dependency failed

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

The normalized v1 response contract can return 424 when the read service is unavailable.

<Note>
  **Related.** [Create extraction](/api-reference/extractions/create) with `verified_follower_explorer` for saved verified follower jobs, [Export extraction](/api-reference/extractions/export) for CSV, JSON, or XLSX downloads, [Get followers](/api-reference/x/followers), [Get following](/api-reference/x/following), and [Get followers you know](/api-reference/x/followers-you-know).
</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.