Skip to main content
This guide builds on the Go SDK setup, which covers install and authentication.

Follower export workflow to CSV, JSON, or XLSX

Use this workflow when a Go worker needs an owned follower list. It feeds CRM imports, warehouse loads, analyst CSVs, XLSX workbooks, or resumable JSON handoffs. The workflow calls POST /extractions/estimate through client.Extractions.EstimateCost and creates the job with client.Extractions.Run. It reads saved rows with client.Extractions.Get and downloads files with client.Extractions.ExportResults.
client.Extractions.Run returns the queued 202 Accepted receipt from POST /extractions. Go exposes REST id, toolType, and status: "running" as job.ID, job.ToolType, and job.Status. Store job.ID immediately, then poll client.Extractions.Get before reading pages or calling client.Extractions.ExportResults. Credit reservation happens after the job starts. Available credits can change after EstimateCost. If they did, the run can fetch only the affordable count before export. In that case it can instead mark the job failed with insufficient_credits.
follower_explorer requires TargetUsername. Store job.ID, targetUsername, estimate.EstimatedResults, and estimate.Source before polling. With them, a worker restart can resume the same follower export. client.Extractions.Get returns Results, HasMore, and NextCursor. Pass NextCursor back as Cursor when you need stored JSON pages before exporting files. Use xquik-followers.jsonl for queue replay or warehouse loads and xquik-followers.json for app ingestion. Use xquik-followers.csv for CRM import and xquik-followers.xlsx for analyst handoff. Map exported User ID or row xUserId as the CRM unique key. The cost is 1 credit per follower extracted or returned. Exports are free after the extraction job exists.

Next steps