Skip to main content
GET https://xquik.com/api/v1/x/users/{id}/verified-followers 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. 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 · Supports guest paid reads
Get verified followers returns verified profiles that follow one X account. Name the account by username or numeric user ID. The endpoint is GET /api/v1/x/users/{id}/verified-followers.
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.
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

For one JSON page of a user’s verified followers now, use GET /x/users/{id}/verified-followers. It suits a CRM, warehouse, scoring, enrichment, or agent workflow. The endpoint accepts a username or numeric user ID. It returns verified follower profile rows with cursor fields. For estimated jobs, saved extractions, or CSV, JSON, or XLSX file export, use verified_follower_explorer.

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

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

Query parameters

Choose fields

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.

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

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.

400 Invalid user ID

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

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

You exceeded your tier rate limit. 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. See also Get followers, Get following, and Get followers you know.

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": "user_not_found", "message": "X user not found. Check the username." }
  • 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." }