Skip to main content
GET
Twitter verified followers API & profile export
Retrieve verified profiles that follow one X account. Store stable user IDs, handles, verification types, counts, and pagination cursors.
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.
1 credit per result returned · All plans from $0.00012/credit · Supports guest paid reads
Get verified followers returns verified profiles that follow one X account by username or numeric user ID. It is also useful as a verified followers API, X verified followers API, or Twitter verified followers API. The canonical endpoint remains GET /api/v1/x/users/{id}/verified-followers.
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.
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. 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. Finished, expired, superseded, or identity-mismatched cursors return 410 coverage_cursor_gone. The response omits Retry-After. Restart without a cursor. Deduplicate restarted results by id. Malformed cursors return 400 invalid_coverage_cursor. Restart without them.
The Node.js and Python snippets shape durable verified follower rows instead of printing the full response page. Persist verifiedRows or verified_rows with the checkpoint so a worker can resume pagination with next_cursor without duplicating already 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 either a username or numeric user ID and returns verified follower profile rows with cursor fields. Use verified_follower_explorer when you need an estimated job, saved extraction, or CSV/JSON/XLSX file export.

Verified rows

Store users[] as the verified follower profile rows returned on this page.

Stable upserts

Store users[].id as x_user_id for CRM, warehouse, scoring, and agent dedupe.

Readable labels

Store users[].username and users[].name for handles, labels, enrichment, and review queues.

Verification signals

Store users[].verified and verifiedType to segment standard, business, and government accounts.

Audience signals

Store users[].followers, users[].following, and statusesCount for scoring and prioritization.

Profile enrichment

Store users[].description, location, url, profilePicture, and coverPicture when returned.

Next page

Store has_next_page and next_cursor; pass next_cursor back as cursor only when has_next_page is true.
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.

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. Export fields such as user ID, username, profile name, biography, location, verification state, and follower counts. Save the cursor and collection time with each page. 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. Compare snapshots by user ID. Do not use username changes as new follower events. Keep the complete followers endpoint separate when analysis needs the entire audience. Paginate until no next cursor remains. Deduplicate resumed exports by source account and follower ID.

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 a reviewed downstream process. Use stable follower IDs for CRM upserts. Treat usernames, names, biographies, images, verification, and counts as replaceable profile attributes. Keep rejected import rows for review. Choose direct cursor pages for current application reads. Choose verified_follower_explorer for estimates, saved jobs, and downloadable CSV, JSON, or XLSX files. Record which path created every directory snapshot.

Validate verified follower export completeness

Save every page before advancing its opaque cursor. Request another page only when has_next_page is true. Pass next_cursor back unchanged. Deduplicate resumed pages by source account ID and follower user ID. Keep the newest complete profile fields. Preserve 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. Refresh verification before time-sensitive segmentation. Verification can change after collection. Keep the collection time beside every exported row.

Path parameters

string
required
User ID (numeric) or username.

Query parameters

string
Pass next_cursor back unchanged. New Xquik cursors resume automatic coverage. Existing unprefixed cursors keep legacy behavior.
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.
string
Legacy cursor alias. Use cursor; when both are present, cursor wins.
number
Automatic pages accept 20 through 300. Standard pages accept 20 through 200. The default is 200. Sources can return fewer profiles.
number
With mode=coverage, set a one-shot cap from 1 through 10000. Otherwise, this is a legacy page size alias. pageSize wins.

Which verified follower endpoint?

Verified followers

Use GET /x/users/{id}/verified-followers for verified accounts that follow one profile.

All followers

Use GET /x/users/{id}/followers when you need verified and unverified followers.

Following list

Use GET /x/users/{id}/following for accounts the profile follows.

Saved exports

Use verified_follower_explorer for a saved verified follower extraction with CSV, JSON, or XLSX download handoff.

User result filters

These filters apply before billing. Selective filters can return fewer rows.
integer
Require this minimum follower count. Filtering happens before billing.
integer
Allow this maximum follower count. Missing counts pass this filter.
integer
Require this minimum following count.
integer
Allow this maximum following count. Missing counts pass this filter.
integer
Require this minimum post count.
integer
Allow this maximum post count. Missing counts pass this filter.
integer
Require this minimum account age in days.
boolean
When true, only return verified profiles.
string
Match the exact verification type.
boolean
When true, require a profile website.
boolean
When true, require a profile location.
string
Require every comma-separated or line-separated bio term.
string
Require this text in the profile location.
string
Require this text in the username.

Headers

string
Full account key. Sessions and OAuth also work.
string
Bearer xq_your_guest_key_here for paid_reads.

Response

200 OK

object[]
Array of verified follower profiles. User object fields.
string
X user ID.
string
X username.
string
Display name.
string
Profile bio. Omitted if empty.
number
Follower count.
number
Following count.
boolean
Whether the user is verified. Always true for this endpoint.
string
Verification type (e.g. Business, Government). Omitted for standard blue check.
string
Profile picture URL.
string
Profile location. Omitted if empty.
string
ISO 8601 account creation timestamp.
number
Total number of tweets posted. Omitted if unavailable.
string
Cover/banner image URL. Omitted if unavailable.
number
Total number of media tweets posted. Omitted if unavailable.
string
Website URL from profile. Omitted if empty.
number
Total number of tweets liked. Omitted if unavailable.
boolean
Whether the user has custom timelines. Omitted if unavailable.
boolean
Whether the user is an X translator. Omitted if unavailable.
string[]
Country codes where the account is withheld. Omitted if empty.
boolean
Whether the account is flagged as possibly sensitive. Omitted if unavailable.
string[]
IDs of pinned tweets. Omitted if none.
boolean
Whether the account is marked as automated. Omitted if unavailable.
string
Username of the account operator if automated. Omitted if not automated.
boolean
Whether the account is unavailable. Omitted if available.
string
Reason the account is unavailable. Omitted if available.
object
Structured profile bio with entity annotations. Omitted if unavailable.
boolean
Whether the account has X Premium verification. Omitted if unavailable.
boolean
Normalized verification status. Omitted if unavailable.
string
Profile banner URL. Omitted if unavailable.
boolean
Whether the account protects its posts. Omitted if unavailable.
string
Role within the requested community context. Omitted outside community results.
boolean
Whether more results are available.
string
Cursor for the next page.

400 Invalid user ID

404 User not found

401 Unauthenticated

Anonymous requests get WWW-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

Your tier rate limit was exceeded. Wait for the Retry-After header before retrying.

424 Dependency failed

The normalized v1 response contract can return 424 when the read service is unavailable.
Related. Create extraction with verified_follower_explorer for saved verified follower jobs, Export extraction for CSV, JSON, or XLSX downloads, Get followers, Get following, and Get followers you know.