# 🧵✨ Threads User Followers Scraper (`scraper-engine/threads-user-followers-scraper`) Actor 🧵✨ Threads User Followers Scraper extracts followers from public Threads profiles. Gather usernames, profile URLs, bios, follower counts, and other public account data in structured output. Ideal for influencer research, audience analysis, lead generation, and competitor tracking. - **URL**: https://apify.com/scraper-engine/threads-user-followers-scraper.md - **Developed by:** [Scraper Engine](https://apify.com/scraper-engine) (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 $4.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 🧵✨ Threads User Followers Scraper is an Apify actor that turns Threads profile links or @usernames into structured follower lists — fast. It solves the “export followers without an official API” problem by combining profile HTML parsing with JS bundle doc_id discovery and web GraphQL, making it a dependable Threads followers scraper and Meta Threads followers extractor for scale. Built for creators, marketers, developers, data analysts, and researchers, it helps you automate influencer research, audience analysis, lead generation, and competitor tracking — all in a single run. ### What data / output can you get? | Data field | Description | Example value | | --- | --- | --- | | username | The follower’s Threads handle | "baselad21" | | full_name | Display name from the profile | "Bassel Kaddour" | | user_id | Threads user ID (stringified) | "73956966771" | | pk | Primary key (stringified) | "73956966771" | | profile_url | Canonical profile URL | "https://www.threads.net/@baselad21" | | is_verified | Verification badge flag | false | | is_private | Whether the Threads profile is private | false | | follower_count | Follower count for the profile | 1 | | profile_pic_url | Avatar image URL | "https://..." | | following | Whether the target account follows this user | false | | followed_by | Whether this user follows the target account | false | | outgoing_request | Whether there’s an outgoing follow request | false | Notes: - Each dataset item includes additional metadata for completeness: source, target_username, has_onboarded_to_text_post_app, and __typename. - Export your dataset to CSV, JSON, or Excel from the Apify platform for analysis or CRM import. ### Key features - 🚀 Bulk profile input Paste multiple Threads profile URLs or @usernames to run large exports in one go — perfect for Threads user followers list export and Threads profile followers export. - 🔐 Session-based access (required) Uses your session cookie (sessionId) to fetch the same public data you can see while logged in. No passwords, just a cookie value — a practical Threads followers API alternative. - 🌐 Smart proxy ladder with sticky residential Starts direct, then falls back to Apify datacenter, then residential (up to 3 attempts). When residential succeeds, it sticks to residential for the rest of the run for maximum stability — ideal for scraping Threads followers without API friction. - 📡 Web GraphQL + JS token strategy Automatically extracts app_id, csrf token, user_id, and doc_id from profile HTML and JS bundles, then fetches followers in batched queries for reliable, repeatable results. - ⏱️ Rate-limited batching and dedupe Batches of 50 followers per request with ~0.35s pacing, stopping after 10 consecutive rounds with no new unique followers. Built-in deduplication ensures clean, unique rows. - 📤 Live dataset streaming Each follower record is pushed to the Dataset as soon as it’s discovered for real-time monitoring and incremental Threads followers CSV export. - 🧰 Developer-friendly on Apify Run via the Apify UI or programmatically through Apify’s API/SDK. Easy to plug into downstream automations for Threads follower crawler bot workflows. - ⚙️ Configurable proxy options Provide proxyConfiguration if you need custom networking; otherwise, the defaults are optimized for stability. ### How to use 🧵✨ Threads User Followers Scraper — step by step 1) Sign in to Apify and open the 🧵✨ Threads User Followers Scraper actor. 2) Collect your session cookie. In your browser, open cookie settings for Instagram or Threads, find sessionid, and copy its value. 3) Add profiles in urls. You can paste: - @usernames (e.g., @zuck) - Full profile URLs (e.g., https://www.threads.com/@creator or https://www.threads.net/@creator) Mix and match as needed. 4) Paste your sessionId into the “Your logged-in session (required)” field. Keep it secret. 5) Set maxFollowers to control how many unique followers to collect per profile. Use samples for speed or higher numbers for deeper exports. 6) (Optional) Configure proxyConfiguration if you need custom proxy behavior. Otherwise, leave it to defaults — the actor will automatically apply a proxy ladder when needed. 7) Run the actor. You’ll see rows appear in the Dataset in real time as the Threads user followers data scraper fetches results. 8) Download your results from the run’s Dataset in CSV, JSON, or Excel for analysis or workflows. Pro Tip: Running locally? Set APIFY_TOKEN in your environment so proxy fallbacks can authenticate smoothly, then execute via apify run or python -m src with an INPUT.json for testing. ### Use cases | Use case | Description | | --- | --- | | Influencer research & discovery | Identify and analyze who follows key creators to refine outreach and partnership strategies. | | Competitor followers scraping | Export competitor follower lists to benchmark audiences and spot high-intent segments. | | Audience analysis & segmentation | Build structured datasets for clustering by follower_count, verified status, and privacy flags. | | Lead generation & enrichment | Enrich CRM records with Threads profile URLs and usernames from target audiences. | | Academic & market research | Collect public follower graphs to study networks, communities, and trends at scale. | | Developer pipelines (API/SDK) | Automate a Threads follower crawler bot workflow by fetching datasets via the Apify API for ETL and analytics. | ### Why choose 🧵✨ Threads User Followers Scraper? This Instagram Threads followers scraping tool is engineered for precision, stability, and automation at scale. - 🎯 Accurate token handling: Extracts app_id, csrf token, user_id, and doc_id from HTML/JS for robust GraphQL queries. - 📈 Built for scale: Batch requests (50 at a time), with ~0.35s pacing and early-stop logic to optimize throughput. - 🔄 Resilient networking: Auto-switches from direct to datacenter to residential proxies and stays on residential if it works best. - 💾 Real-time dataset output: See results as they’re collected and export to CSV/JSON/Excel for quick wins. - 👨‍💻 API/SDK friendly: Runs on Apify infrastructure and integrates easily into your data pipelines. - 🔐 Privacy-first session model: Uses your sessionId cookie; you only access what your account can see. - 💰 Cost control: Tune maxFollowers per profile to manage volume and spend. In short, it’s a reliable Threads followers lookup tool designed to outperform fragile, manual approaches. ### Is it legal / ethical to use 🧵✨ Threads User Followers Scraper? Yes — when used responsibly. This actor collects public account data accessible to your logged-in session. You’re responsible for ensuring your use complies with Threads/Meta terms and applicable laws. Guidelines: - Only scrape data you’re allowed to access with your account. - Avoid collecting sensitive or non-public information. - Respect platform rate limits and usage policies. - Align with data protection laws (e.g., GDPR, CCPA) in your jurisdiction. - Consult your legal team for edge cases or regulated uses. ### Input parameters & output format #### Example input ```json { "urls": ["@zuck", "https://www.threads.net/@creator"], "sessionId": "YOUR_SESSIONID_COOKIE_VALUE", "maxFollowers": 20, "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.\ Default: none (required) - sessionId (string, required)\ Description: Your logged-in session cookie value sessionid from Instagram or Threads. Keep it secret; treat it like a password. With a valid session, you’ll only see data your account is allowed to view.\ Default: "" - maxFollowers (integer, optional)\ Description: Set a cap on how many follower rows to collect for each profile. Useful for sampling or deep exports; reasonable limits keep runs smooth.\ Default: 20\ Range: 1–100000 - proxyConfiguration (object, optional)\ Description: Network options (optional). Leave defaults if unsure; Apify proxy settings help keep things stable from the cloud. Power users can tweak as needed.\ Default: { "useApifyProxy": true } #### Example output item ```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: - Field defaults: When a value is missing, strings may be "", booleans default to false, and numbers default to 0 as per node\_to\_record logic. - The actor deduplicates records by pk/user\_id or @username, and pushes each unique follower row as it’s discovered. ### FAQ #### Do I need to log in or provide credentials? ✅ Yes. You must provide a sessionId cookie value (sessionid) from Instagram or Threads. The actor never asks for your password and only uses your session to access data your account can see. #### What profiles can it scrape? ✅ It supports @usernames and profile URLs from both threads.com and threads.net. The input parser accepts plain handles like @zuck or full links like https://www.threads.net/@creator. #### How many followers can I export per profile? 📈 Controlled by maxFollowers. The actor batches 50 followers per request, paces ~0.35s between rounds, and stops after 10 consecutive rounds with no new unique followers. #### Does it use an official API? ❌ No. It’s a Threads followers API alternative. It extracts required tokens from profile HTML/JS (including doc\_id) and then uses web GraphQL to fetch followers — a reliable way to scrape Threads followers without API access. #### Will it work without proxies? 🔄 It tries direct connections first. If that fails, it falls back to Apify datacenter proxies and then residential proxies (up to 3 attempts). Once residential works, it sticks to it for the rest of the run for stability. #### Can it scrape private accounts? ⚠️ Only if your session has permission to see them. The actor uses your sessionId cookie and respects whatever access your logged-in account has. #### What data fields are included in the output? 🧾 You’ll get username, full\_name, user\_id, pk, profile\_url, is\_verified, is\_private, follower\_count, profile\_pic\_url, and friendship flags (following, followed\_by, outgoing\_request), plus metadata like source, target\_username, has\_onboarded\_to\_text\_post\_app, and \_\_typename. #### How do I export the results? 💾 Download from the run’s Dataset in your preferred format (CSV, JSON, or Excel) for Threads followers CSV export and downstream automation. ### Final thoughts 🧵✨ Threads User Followers Scraper is built to export clean, structured follower lists from public Threads profiles at scale. With session-based access, a resilient proxy ladder, GraphQL batching, and live dataset streaming, it’s ideal for marketers, researchers, developers, and analysts. Configure urls, sessionId, and maxFollowers, then integrate the Dataset via the Apify API to automate your Threads followers scraping tool workflows. Start extracting smarter audience insights and power your outreach, enrichment, and analytics with dependable follower data. # 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("scraper-engine/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("scraper-engine/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 scraper-engine/threads-user-followers-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraper-engine/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 followers from public Threads profiles. Gather usernames, profile URLs, bios, follower counts, and other public account data in structured output. Ideal for influencer research, audience analysis, lead generation, and competitor tracking.", "version": "0.1", "x-build-id": "8DSj86hOk79tbm4LT" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraper-engine~threads-user-followers-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraper-engine-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/scraper-engine~threads-user-followers-scraper/runs": { "post": { "operationId": "runs-sync-scraper-engine-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/scraper-engine~threads-user-followers-scraper/run-sync": { "post": { "operationId": "run-sync-scraper-engine-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 } } } } } } } } } } ```