🧵✨ Threads User Followers Scraper — Export Follower Lists with Profiles & Verification

Export the follower list of any Threads profile. Paste profile links or plain usernames and get one row per follower with their username, full name, follower count, verification badge, private-account flag, profile picture, profile URL — and the relationship flags between them and your own account.

Bulk profiles, per-profile caps, and every row labelled with the account it came from.

---

What you get

👤 Identity	📊 Audience	🔗 Relationship
Username and full name	Their follower count	Whether you follow them
User ID and PK		Whether they follow you
Profile URL		Outgoing follow request pending
Profile picture		Onboarded to Threads flag
Verified badge		Source profile (target_username)
Private-account flag

---

Key features

• Follower lists at scale. One or many profiles per run, each with its own cap, and every row tagged with target_username so a multi-profile export stays perfectly attributable.
• Follower counts on every follower. Each row includes that person's own follower count — so you can immediately rank an audience by influence rather than treating all followers as equal.
• Verification and privacy flags. is_verified and is_private let you filter a list down to reachable, credible accounts in one step.
• Relationship flags. following, followed_by and outgoing_request are relative to your authenticated account, so you can exclude people you already follow or have already requested.
• Onboarding flag. has_onboarded_to_text_post_app distinguishes accounts genuinely active on Threads from Instagram accounts that were carried over.
• Usernames or links. @zuck, zuck and https://www.threads.com/@creator are all accepted, mixed freely.
• Privacy-first authentication. No password is ever requested — only your own browser sessionid cookie, so the Actor sees exactly what you already see when logged in.
• Optional Apify Proxy for extra stability when running from the cloud.

---

Use cases

• Audience research — understand who actually follows an account, and how big their own audiences are.
• Influencer discovery — a niche authority's follower list is dense with adjacent creators and engaged people.
• Competitor analysis — export a competitor's followers to see who they reach.
• Lead generation — followers of a niche account are pre-qualified by interest.
• Community mapping — run several accounts and find the people who follow all of them.
• Audience overlap analysis — intersect two follower lists to measure shared reach.
• Outreach list building — filter out private accounts and people you already follow before you start.
• Growth tracking — schedule runs and compare follower lists over time to see who joined and who left.

---

How it works

1. You supply profile links or usernames and your Threads/Instagram sessionid cookie.
2. Each profile is resolved to its user ID.
3. The follower list is paged through Threads' own cursor, up to your per-profile cap.
4. Every follower is normalised into a flat record with identity, audience size, flags and profile URL.
5. Rows stream into the dataset as they are collected, each labelled with the source profile.

---

Quick start

1. Log in to Threads (or Instagram) in your browser.
2. Open your browser's cookie settings, find sessionid, and copy its value.
3. Paste it into the Actor's session field.
4. Add your profiles and set How many people per profile.
5. Click Start, then export the Output tab as CSV, Excel or JSON.

Minimal input

{
  "urls": ["zuck"],
  "sessionId": "<YOUR_SESSIONID_COOKIE>",
  "maxFollowers": 100
}

---

Input configuration

Field	Type	Default	Description
urls	array	— (required)	Threads profile links or plain usernames, one per line. @zuck, zuck and https://www.threads.com/@creator all work.
sessionId	string	— (required)	Your sessionid cookie from Instagram or Threads. It tells Threads you are you — the Actor only ever sees what your account is allowed to see.
maxFollowers	integer	20	Cap on follower rows collected per profile.
proxyConfiguration	object	Apify Proxy	Optional. Helpful for extra stability when running from the cloud; safe to leave at the default.

⚠️ Your session cookie is a credential. Treat it like a password — never share it or paste it into public chats or repositories. Use a dedicated secondary account where possible, and note that automated activity can lead Meta to restrict accounts. Cookies expire; refresh the value if runs start returning nothing.

---

Output data

One row per follower.

Field	Type	Description
username	string	Follower's username.
full_name	string	Display name.
user_id, pk	string	Threads user identifiers.
profile_url	string	Direct link to their profile.
profile_pic_url	string	Profile picture URL.
follower_count	number	How many followers they have.
is_verified	boolean	Verification badge.
is_private	boolean	Whether their account is private.
following	boolean	Whether you follow them.
followed_by	boolean	Whether they follow you.
outgoing_request	boolean	Whether you have a pending follow request to them.
has_onboarded_to_text_post_app	boolean	Whether they have actually onboarded to Threads.
target_username	string	Whose follower list this row came from.
source	string	Always threads.
__typename	string	Underlying record type.

Example output

{
  "source": "threads",
  "target_username": "zuck",
  "user_id": "3141592653",
  "pk": "3141592653",
  "username": "exampleuser",
  "full_name": "Example User",
  "profile_url": "https://www.threads.net/@exampleuser",
  "profile_pic_url": "https://scontent.cdninstagram.com/…",
  "follower_count": 18420,
  "is_verified": false,
  "is_private": false,
  "following": false,
  "followed_by": false,
  "outgoing_request": false,
  "has_onboarded_to_text_post_app": true,
  "__typename": "XDTUserDict"
}

Illustrative values — a live run returns current Threads data.

---

Usage examples

One profile, deep export

{
  "urls": ["yourcompetitor"],
  "sessionId": "<YOUR_SESSIONID_COOKIE>",
  "maxFollowers": 2000
}

Several accounts at once

{
  "urls": ["accountone", "@accounttwo", "https://www.threads.com/@accountthree"],
  "sessionId": "<YOUR_SESSIONID_COOKIE>",
  "maxFollowers": 500
}

Build a reachable outreach list

Run any profile, then filter your export for is_private: false, following: false and has_onboarded_to_text_post_app: true — public, active accounts you have not already contacted.

Find the influential followers

Sort your export by follower_count descending — the top of that list is who to prioritise.

Audience overlap

Run two competitors and intersect the exports on user_id. The overlap is the audience both are competing for.

Growth tracking

Save the input as a Task, attach a weekly Schedule, and diff user_id sets between runs to see gains and losses.

---

Run it from your own code

Python

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_API_TOKEN>")

run = client.actor("scraperx/threads-user-followers-scraper").call(run_input={
    "urls": ["zuck"],
    "sessionId": "<YOUR_SESSIONID_COOKIE>",
    "maxFollowers": 500,
})

for f in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(f["username"], "|", f["follower_count"], "| verified:", f["is_verified"])

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_API_TOKEN>' });

const run = await client.actor('scraperx/threads-user-followers-scraper').call({
    urls: ['zuck'],
    sessionId: '<YOUR_SESSIONID_COOKIE>',
    maxFollowers: 500,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

cURL

curl -X POST "https://api.apify.com/v2/acts/scraperx~threads-user-followers-scraper/runs?token=<YOUR_APIFY_API_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"urls":["zuck"],"sessionId":"<YOUR_SESSIONID_COOKIE>","maxFollowers":500}'

Integrations

Push followers into Google Sheets, Airtable, Slack, Make, Zapier, Google Drive or your CRM via webhooks, and use Schedules to track audience growth over time.

---

Pricing

Pay-per-event: a small Actor-start charge plus a charge per follower row delivered to your dataset. maxFollowers is the cost lever — start small to validate your filters, then scale.

Current rates are on the Pricing tab of this Actor's page, and Apify shows an estimate before and during every run. If you enable residential proxies, that traffic is billed separately by the platform.

---

Limits & good to know

• A valid sessionid is required. Follower lists are not available anonymously. Expired cookies are the most common cause of an empty run — refresh the value from your browser.
• You only get what your account can see. The Actor never elevates access beyond your own session.
• maxFollowers is per profile, so three profiles at 500 each can return up to 1,500 rows.
• Public profiles only. Private accounts do not expose their follower lists.
• Relationship flags are relative to your account — following means you follow them.
• has_onboarded_to_text_post_app matters. Some followers are Instagram accounts that never activated Threads; filter them out for outreach.
• Profile picture URLs point at Meta's CDN and expire — download promptly if you need the files.
• Pace large jobs and use a dedicated secondary account; automated access can lead Meta to restrict accounts.
• Default run options are 4 GB memory and a 1-hour timeout — raise the timeout for very large exports.

---

FAQ

Do I need my password? No — never. Only your own sessionid browser cookie.

Where do I find sessionid? Log in to Threads or Instagram, open your browser's cookie settings for that site, and copy the value of sessionid.

Can I scrape private accounts? No. Only public profiles expose their follower lists.

Can I scrape following lists as well? This Actor covers followers. Following lists require a different endpoint.

What do following and followed_by mean? They describe the relationship between your authenticated account and that follower — useful for filtering out people you already follow.

Why is a follower count zero? Threads did not report one for that account; treat it as unavailable rather than genuinely zero.

How many followers can I export? As many as your cap allows and the profile actually has — set maxFollowers per profile.

Which export formats are supported? JSON, CSV, Excel (XLSX), XML and RSS. CSV works perfectly — the rows are flat.

---

Legal & responsible use

This Actor reads follower lists that Threads shows to a logged-in user — your own session, no elevation, no bypass. Usernames, names, avatars and follower relationships are personal data about identifiable people. If you process them, ensure you have a lawful basis under GDPR and comparable regulations, honour opt-outs when doing outreach, and comply with Meta's terms. You are responsible for the account whose cookie you supply, including Meta's restrictions on automated access.

Support

Need following lists, extra fields, or a custom Threads audience-research pipeline? Open an issue on the Issues tab of this Actor.