Follower export workflow to CSV, JSON, or XLSX
This workflow is for a .NET worker, console job, or ASP.NET background service. Use it when that code needs an owned follower list. It feeds CRM imports, warehouse loads, analyst CSVs, XLSX workbooks, or resumable JSON handoffs.client.Extractions.EstimateCost and client.Extractions.Run map to the extraction workflow. For follower exports, use ExtractionEstimateCostParamsToolType.FollowerExplorer and ExtractionRunParamsToolType.FollowerExplorer. follower_explorer requires TargetUsername. client.Extractions.Retrieve returns Results, HasMore, and NextCursor for pagination. client.Extractions.ExportResults returns an HttpResponse. Read CSV and JSON as strings, and copy XLSX from the response stream.client.Extractions.Run returns the queued 202 Accepted receipt from POST /extractions. C# exposes REST id, toolType, and status: "running" as job.ID, job.ToolType, and job.Status. Store job.ID immediately, then poll client.Extractions.Retrieve 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.job.ID, targetUsername, estimate.EstimatedResults, and estimate.Source before polling. With them, a queue retry can resume the same follower export. So can a Windows service restart or worker restart. Keep page.NextCursor as the checkpoint when you stream followers to JSON Lines. Map exported User ID or row xUserId as the CRM unique key. 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. Exports are free after the extraction job exists.