# 🧵✨ Threads user followers scraper (`scrapier/threads-user-followers-scraper`) Actor 🧵✨Threads user followers scraper extracts and maps follower relationships on Threads—followers, following, and mutuals. 🔎 Ideal for audience mapping, competitor research, and influencer outreach. 📊 Export CSV/JSON, schedule runs, and integrate via API. - **URL**: https://apify.com/scrapier/threads-user-followers-scraper.md - **Developed by:** [Scrapier](https://apify.com/scrapier) (community) - **Categories:** Social media, Lead generation, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, NaN bookmarks - **User rating**: No ratings yet ## Pricing from $5.99 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ### 🧵✨ Threads user followers scraper The 🧵✨ Threads user followers scraper is a production-ready Apify actor that extracts structured follower lists from Threads profiles in bulk using GraphQL with HTML token discovery. It solves the tedious task of collecting audience data by turning profile URLs or @usernames into clean records — ideal for audience mapping, competitor research, and influencer outreach. Marketers, developers, data analysts, and researchers can use this Threads followers scraper to download Threads followers lists, export CSV/JSON, schedule runs, and integrate via API at scale. ### What data / output can you get? Below are the exact fields this Threads followers exporter tool saves to the Dataset. You can export results as CSV or JSON, or access them via the Apify API. | Data type | Description | Example value | | --- | --- | --- | | source | Data source indicator | "threads" | | target_username | Username of the profile whose followers are being collected | "zuck" | | user_id | Follower’s Threads user ID | "73956966771" | | pk | Follower primary key (same as user_id in most cases) | "73956966771" | | username | Follower’s handle | "baselad21" | | full_name | Follower’s display name | "Bassel Kaddour" | | is_verified | Whether the follower is verified | false | | is_private | Whether the follower’s Threads app is private | false | | profile_pic_url | URL to follower’s profile picture | "https://..." | | follower_count | Number of followers that user has | 1 | | following | Friendship flag from the session’s perspective | false | | followed_by | Friendship flag from the session’s perspective | false | | outgoing_request | Whether there’s an outgoing follow request | false | | has_onboarded_to_text_post_app | Threads onboarding flag | true | | __typename | Backend type identifier | "XDTUserDict" | | profile_url | Normalized Threads profile URL | "https://www.threads.net/@baselad21" | Note: Some fields may be empty strings, false, or 0 if not provided by Threads. Export the dataset to CSV or JSON for analysis, CRM uploads, or reporting. ### Key features - 🔁 Resilient proxy ladder Starts direct (no proxy), then automatically tries Apify datacenter proxy, then residential (up to 3 attempts). Once residential succeeds, it sticks to residential for the rest of the run for stability. Ideal for reliable Meta Threads followers scraping at scale. - 🔐 Session-based accuracy Requires a valid sessionid cookie (input sessionId). This approach mirrors what you can access while logged in, enabling accurate follower retrieval with friendship flags like following and followed_by. - 📦 Bulk input, live streaming output Feed multiple profile URLs or @usernames and process them in one run. Each follower is pushed to the Dataset as soon as it’s discovered — perfect for a bulk Threads followers scraper and real-time pipelines. - ⚙️ GraphQL-driven, deduped records Uses GraphQL with HTML/JS token extraction (app_id, doc_id, CSRF). Requests are paced (~0.35s between rounds) with batches of first=50 and stop after 10 consecutive rounds with no new unique followers, ensuring stable, clean datasets. - 🧰 Developer-friendly API Integrate results via the Apify API or use this Threads followers API programmatically. Works great in Python-based automation and data workflows. - 💾 Flexible exports Download Threads followers list as CSV or JSON from the Dataset. Use it for analysis, enrichment, and reporting. - 🧱 Production-ready infrastructure Built on Apify’s platform with smart retry logic, proxy management, and dataset storage — more reliable than a Threads followers scraper Chrome extension or ad-hoc scripts. ### How to use 🧵✨ Threads user followers scraper - step by step 1. Create or log in to your Apify account. 2. Open the actor and prepare your input. - Paste @usernames or profile URLs into urls (one per line is fine). - Obtain your sessionId cookie value from your browser (Instagram or Threads), then paste it into sessionId. 3. Set maxFollowers per profile as needed (the input form default is 20; if omitted entirely in code, the run caps at 200). 4. (Optional) Configure proxyConfiguration if you need custom proxy behavior; otherwise, leave defaults. 5. Start the run. - The actor resolves tokens from the profile page (app_id, doc_id, CSRF), then fetches followers in GraphQL batches of 50 with ~0.35s delays. - It deduplicates by user pk/user_id and stops after 10 consecutive rounds with no new unique followers. - Rows stream into the Dataset as they’re collected. 6. Download your results. - Go to the Dataset tab and export to CSV or JSON, or fetch via the API. 7. Pro Tip: Schedule runs and wire the Dataset API into your workflows for a no-code Threads followers scraper pipeline (e.g., automate weekly refreshes and downstream processing). ### Use cases | Use case | Description | | --- | --- | | Audience mapping for creators | Build a clean follower roster to understand who follows key profiles; export CSV for segmentation and targeting. | | Competitor research for marketers | Compare follower bases across rivals using a Threads profile followers scraper and track changes over time. | | Influencer outreach lists | Use this Threads followers exporter tool to collect verified flags, follower counts, and profile URLs for qualified outreach. | | Data enrichment via API | Pipe followers into internal systems using the Apify API from this Threads followers API workflow. | | Academic & social research | Analyze network patterns and public signals (verified/private, follower counts) at scale. | | Bulk list builds | Run multiple profiles at once with a bulk Threads followers scraper for campaign planning or CRM enrichment. | ### Why choose 🧵✨ Threads user followers scraper? This Meta Threads followers scraper focuses on precision, stability, and automation for production workflows. - 🎯 Accurate, structured output using GraphQL tokens and HTML/JS parsing - 📈 Built for scale with bulk inputs and streaming datasets - 💻 Developer access via Apify API; a great fit for Threads followers scraper Python workflows - 🔐 Session-based design respects visibility you already have while logged in - 🌐 Smart network strategy with a proxy ladder and sticky residential fallback - 💾 Easy exports to CSV/JSON for ops, analytics, and reporting - 🧱 More robust and consistent than browser-based extensions or unstable one-off scripts In short: a reliable Threads followers scraper that’s automation-ready and designed for real-world data pipelines. ### Is it legal / ethical to use 🧵✨ Threads user followers scraper? Yes — when done responsibly. This actor requires your session cookie and accesses only what your account can see while logged in. Guidelines to follow: - Only collect data you are allowed to access and process. - Review and respect Threads/Meta terms of service. - Ensure compliance with data protection regulations (e.g., GDPR, CCPA) and your organization’s policies. - Avoid misuse (e.g., spam); use results for legitimate research, enrichment, or analysis. - Consult your legal team for edge cases or sensitive use. ### Input parameters & output format Example JSON input ```json { "urls": [ "https://www.threads.com/@zuck", "@creator_handle" ], "sessionId": "YOUR_SESSIONID_COOKIE_VALUE", "maxFollowers": 200, "proxyConfiguration": { "useApifyProxy": true } } ```` Parameters - urls (array, required) - Description: Paste Threads links or plain usernames — one per line is fine. Examples: @zuck · https://www.threads.com/@creator · mix & match as you like! Running a big list? Go ahead — that’s what this field is for. - Default: none - sessionId (string, required) - Description: This tells Threads you’re you — same as when you browse the app yourself. Open your browser’s cookie settings for Instagram or Threads, find sessionid, and paste the value here. Keep it secret — treat it like a password. With a valid session, you only get data your account is allowed to see. - Default: "" - maxFollowers (integer, optional) - Description: Set a cap on how many follower rows to collect for each profile in your list. Handy when you only need a sample — or crank it up for a deeper export. Friendly to servers: reasonable limits keep runs smooth for everyone. - Default: 20 - proxyConfiguration (object, optional) - Description: Totally optional — leave the defaults if you’re not sure. When you need extra stability reaching Threads from the cloud, Apify’s proxy settings can help keep things running smoothly. Power users: tweak here; everyone else can skip. - Default: none (prefill uses { "useApifyProxy": true }) Example JSON output ```json { "source": "threads", "target_username": "zuck", "user_id": "73956966771", "pk": "73956966771", "username": "baselad21", "full_name": "Bassel Kaddour", "is_verified": false, "is_private": false, "profile_pic_url": "https://...", "follower_count": 1, "following": false, "followed_by": false, "outgoing_request": false, "has_onboarded_to_text_post_app": true, "__typename": "XDTUserDict", "profile_url": "https://www.threads.net/@baselad21" } ``` Notes: - Fields may be empty/false/0 if not present in the source. - Use the Dataset tab to download Threads followers export CSV or JSON, or fetch via the API. ### FAQ #### Do I need to log in or provide cookies? ✅ Yes. You must provide the sessionid cookie as sessionId. The actor uses your session to access what you can see while logged in. #### Can I download the Threads followers list as CSV or JSON? ✅ Yes. Results are saved to the run’s Dataset. You can export as CSV or JSON, or access them programmatically via the Apify API. #### Does this capture follower IDs? ✅ Yes. Each record includes user\_id and pk, making it suitable as a Threads follower IDs scraper. #### How many followers can it collect per profile? ⚙️ Controlled by maxFollowers. Internally, requests pull batches of 50 with ~0.35s delays and stop after 10 consecutive rounds with no new unique followers. #### Can I run it for multiple profiles at once? ✅ Yes. Add multiple @usernames or profile URLs to urls. It’s a bulk Threads followers scraper designed for batch jobs. #### Is there an API for integration? ✅ Yes. You can consume the Dataset via the Apify API and schedule runs, enabling a Threads followers API workflow for automation. #### Is this a Chrome extension? ❌ No. This is a server-side Apify actor. It’s more reliable than a Threads followers scraper Chrome extension and better suited for automation. #### Can I use the output with Google Sheets? ✅ Yes. Export CSV from the Dataset and import into Google Sheets, or connect via your own workflow. This provides a no-code Threads followers scraper path to Sheets. #### What happens if Threads blocks direct access? 🔁 The actor uses a proxy ladder: direct → Apify datacenter → Apify residential (up to 3 attempts), then sticks to residential once it succeeds for stable throughput. #### What data does it not collect? 🔒 It doesn’t bypass account visibility. Fields come from public endpoints and your session’s allowed view; some properties may be empty if not provided by Threads. ### Closing CTA / Final thoughts The 🧵✨ Threads user followers scraper is built to extract accurate, structured follower data from Threads profiles at scale. With bulk inputs, resilient networking, streaming datasets, and CSV/JSON exports, it’s ideal for marketers, developers, data analysts, and researchers. Use the Apify API for automation-ready pipelines or embed it into Threads followers scraper Python workflows. Start exporting smarter follower lists and power your audience insights, enrichment, and outreach with reliability. # Actor input Schema ## `urls` (type: `array`): 🎯 Paste Threads links **or** plain usernames — one per line is fine. ✨ **Examples:** `@zuck` · `https://www.threads.com/@creator` · mix & match as you like! 📋 Running a big list? Go ahead — that’s what this field is for. ## `sessionId` (type: `string`): 🍪 This tells Threads *you’re you* — same as when you browse the app yourself. 👉 Open your browser’s cookie settings for **Instagram** or **Threads**, find **`sessionid`**, and paste the value here. 🤫 **Keep it secret** — treat it like a password. Never share it or paste it into public chats or code repos. ✅ With a valid session, you only get data your account is allowed to see. ## `maxFollowers` (type: `integer`): 📊 Set a **cap** on how many follower rows to collect for **each** profile in your list. 🛑 Handy when you only need a sample — or crank it up for a deeper export. 💚 **Friendly to servers:** reasonable limits keep runs smooth for everyone. ## `proxyConfiguration` (type: `object`): 🛡️ **Totally optional** — leave the defaults if you’re not sure. ✨ When you need extra stability reaching Threads from the cloud, Apify’s proxy settings can help keep things running smoothly. 🙌 Power users: tweak here; everyone else can skip. ## Actor input object example ```json { "urls": [ "zuck" ], "sessionId": "", "maxFollowers": 20, "proxyConfiguration": { "useApifyProxy": true } } ``` # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "urls": [ "zuck" ], "proxyConfiguration": { "useApifyProxy": true } }; // Run the Actor and wait for it to finish const run = await client.actor("scrapier/threads-user-followers-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "urls": ["zuck"], "proxyConfiguration": { "useApifyProxy": True }, } # Run the Actor and wait for it to finish run = client.actor("scrapier/threads-user-followers-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "urls": [ "zuck" ], "proxyConfiguration": { "useApifyProxy": true } }' | apify call scrapier/threads-user-followers-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scrapier/threads-user-followers-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "🧵✨ Threads user followers scraper", "description": "🧵✨Threads user followers scraper extracts and maps follower relationships on Threads—followers, following, and mutuals. 🔎 Ideal for audience mapping, competitor research, and influencer outreach. 📊 Export CSV/JSON, schedule runs, and integrate via API.", "version": "0.1", "x-build-id": "F5u2eo8cXm4iZNewW" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scrapier~threads-user-followers-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scrapier-threads-user-followers-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/scrapier~threads-user-followers-scraper/runs": { "post": { "operationId": "runs-sync-scrapier-threads-user-followers-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/scrapier~threads-user-followers-scraper/run-sync": { "post": { "operationId": "run-sync-scrapier-threads-user-followers-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "required": [ "urls", "sessionId" ], "properties": { "urls": { "title": "📝 Profiles to look up (one or many)", "type": "array", "description": "🎯 Paste Threads links **or** plain usernames — one per line is fine.\n\n✨ **Examples:** `@zuck` · `https://www.threads.com/@creator` · mix & match as you like!\n\n📋 Running a big list? Go ahead — that’s what this field is for.", "items": { "type": "string" } }, "sessionId": { "title": "🔑✅ Your logged-in session (required)", "type": "string", "description": "🍪 This tells Threads *you’re you* — same as when you browse the app yourself.\n\n👉 Open your browser’s cookie settings for **Instagram** or **Threads**, find **`sessionid`**, and paste the value here.\n\n🤫 **Keep it secret** — treat it like a password. Never share it or paste it into public chats or code repos.\n\n✅ With a valid session, you only get data your account is allowed to see.", "default": "" }, "maxFollowers": { "title": "🎚️ How many people per profile?", "minimum": 1, "maximum": 100000, "type": "integer", "description": "📊 Set a **cap** on how many follower rows to collect for **each** profile in your list.\n\n🛑 Handy when you only need a sample — or crank it up for a deeper export.\n\n💚 **Friendly to servers:** reasonable limits keep runs smooth for everyone.", "default": 20 }, "proxyConfiguration": { "title": "🌐 Network options (optional)", "type": "object", "description": "🛡️ **Totally optional** — leave the defaults if you’re not sure.\n\n✨ When you need extra stability reaching Threads from the cloud, Apify’s proxy settings can help keep things running smoothly.\n\n🙌 Power users: tweak here; everyone else can skip." } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```