Skip to main content

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.

Use this workflow when a sales, support, research, or marketing system needs an owned list of X followers with stable IDs, usernames, display names, verification state, profile images, and enrichment fields.

​
Outcome

StepXquik taskHandoff
EstimatePOST /extractions/estimate with follower_explorerCredit check and projected row count
ExtractPOST /extractions with targetUsername and optional resultsLimitAsync extraction job
RetrieveGET /extractions/{id}Paginated JSON for custom pipelines
ExportGET /extractions/{id}/export?format=csvCSV, XLSX, JSON, Markdown, PDF, TXT, or MD document
ImportMap User ID to a CRM unique fieldCRM import, upsert, segment, or warehouse load

​
Step 1: Estimate cost

Estimate first so the workflow can stop before spending credits. 
curl -X POST https://xquik.com/api/v1/extractions/estimate \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "toolType": "follower_explorer",
    "targetUsername": "elonmusk",
    "resultsLimit": 10000
  }' | jq

{
  "allowed": true,
  "creditsRequired": "10000",
  "creditsAvailable": "77000",
  "estimatedResults": 10000,
  "source": "resultsLimit",
  "resolvedXUserId": "44196397"
}
resultsLimit caps both the estimate and the extraction. Use it for first imports, test segments, and nightly syncs.

​
Step 2: Start the extraction

Run the same request against POST /extractions. 
curl -X POST https://xquik.com/api/v1/extractions \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{
    "toolType": "follower_explorer",
    "targetUsername": "elonmusk",
    "resultsLimit": 10000
  }' | jq

{
  "id": "77777",
  "toolType": "follower_explorer",
  "status": "pending",
  "totalResults": 0,
  "createdAt": "2026-05-08T13:46:00.000Z"
}

​
Step 3: Poll until complete

Poll the job before exporting. Use the paginated endpoint when your pipeline wants JSON rows instead of a file.
cURL
curl -s "https://xquik.com/api/v1/extractions/77777?limit=1000" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
The job is ready for file export when status is completed.

​
Step 4: Export the CRM file

Use CSV for most CRM imports, XLSX for analyst review, or JSON for a data pipeline. 
curl -s "https://xquik.com/api/v1/extractions/77777/export?format=csv" \
  -H "x-api-key: xq_YOUR_KEY_HERE" \
  -o x-followers-elonmusk.csv
Exports are free and capped at 100,000 rows per extraction, with a 10,000-row cap for PDF. Use paginated JSON for larger custom syncs.

​
CRM field mapping

Map stable X identifiers first. Names, bios, and locations can change.
Xquik export columnSuggested CRM fieldWhy it matters
User IDx_user_id custom unique fieldStable X account identifier
UsernameX handle or social profile fieldHuman-readable handle
Display NameName or social display nameUseful for triage and reports
FollowersFollower countSegmentation and priority scoring
VerifiedVerified flagLead scoring or audience filtering
DescriptionBio or notes fieldContext for sales or research
LocationLocation fieldRegional segmentation
Profile ImageAvatar URL fieldEnrichment for internal views

​
Import and upsert rules

Use the CRM’s own unique field rules. HubSpot’s official import docs say update or dedupe imports need a unique identifier, and supported import files include CSV, XLSX, and XLS. Salesforce Bulk API 2.0 upserts use CSV data and require an external ID field for upsert jobs.

HubSpot import docs

Check file requirements, unique identifier rules, and supported spreadsheet formats before importing.

Salesforce Bulk API 2.0

Use CSV upserts with an external ID field when loading large contact or lead datasets.

​
Automation handoff

Use this handoff when the export runs on a schedule:
  1. Store the Xquik extraction ID and source username in your job table.
  2. Poll GET /extractions/{id} until status is completed.
  3. Download format=json for code pipelines or format=csv for CRM import tools.
  4. Upsert by x_user_id, not by display name or username.
  5. Save the Xquik job ID, export format, row count, and import result for audit.

Extraction workflow

Estimate costs, run jobs, paginate results, and export files.

n8n guide

Send extraction rows into Sheets, Slack, and downstream automation.
Last modified on May 8, 2026