Use this workflow when a sales, research, community, or marketing job starts with a topic, brand, creator, or competitor account and needs a scored audience list. Keep every row keyed by X user ID so exports, CRMs, agents, and warehouse loads can dedupe later.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.
Pick the Discovery Path
Keyword Seeds
Use
GET /api/v1/x/users/search?q={query} or people_search to find
candidate profiles by name, handle, or topic.Follower Expansion
Use
follower_explorer or GET /api/v1/x/users/{id}/followers to collect
people who already follow one seed account.Following Expansion
Use
following_explorer or GET /api/v1/x/users/{id}/following to collect
accounts one seed profile follows.Verified Segment
Use
verified_follower_explorer or
GET /api/v1/x/users/{id}/verified-followers when verified accounts should
be scored separately.Seed Accounts
Start with a query when you do not already have exact handles. Store the search query, rank, user ID, username, follower count, verification state, and cursor.Expand the Audience
Use extraction jobs when the output needs estimate, retry, audit, and file download handoff. Use direct JSON pages when the app needs the freshest page now.Saved Followers
POST /api/v1/extractions/estimate, then POST /api/v1/extractions with
toolType: "follower_explorer".Saved Following
Use
toolType: "following_explorer" with targetUsername and optional
resultsLimit.Saved People Search
Use
toolType: "people_search" with searchQuery for reusable profile
search exports.Saved Verified Followers
Use
toolType: "verified_follower_explorer" for a reusable verified
follower export.Direct JSON Pages
Use direct pages when the app owns the loop and checkpoint state.has_next_page and next_cursor with the seed account and route. Pass
next_cursor back as cursor only when has_next_page is true.
Score Rows
Create one normalized row per candidate before enrichment or outreach.Validate Active Conversation
Use tweet search when a candidate segment must be active around a topic before it enters a campaign, CRM list, or agent queue.Cost and Retry Notes
Estimate extraction jobs before running large follower, following, verified
follower, or people search exports.
Direct JSON pages are metered by returned user or tweet rows. Low credit
balances can return smaller pages or
402 insufficient_credits.Treat cursors as opaque route checkpoints. They are not stable profile IDs.
Next Steps
Search Users
Find seed profiles by topic, name, or handle.
Export Followers
Build CSV, JSON, or XLSX follower files for CRM and warehouse handoff.
Get Following
Page accounts followed by one seed profile.
Batch Users
Enrich up to 100 numeric user IDs in one request.