Threads User Following Scraper API

Pricing

Rating

Developer

Actor stats

Categories

Share

Collect the complete following list from any public Threads account — including usernames, full names, verification status, bio links, profile tags, and more. Process up to 10 accounts in a single run.

What does Threads User Following Scraper API do?

This Actor collects the accounts that Threads users follow and returns detailed profile information for each one. You can process multiple usernames in a single run.

For each user, the Actor first returns a profile summary row followed by individual following rows — one per account they follow.

Data you can extract

For the source user (profile row):

• Identity — username, full name, biography, bio links (all URLs from the profile link section)
• Stats — follower count
• Status — verified badge, private account flag, Fediverse federation status
• Media — profile picture (standard and HD)
• Profile enrichment — community/interest tags, linked podcast name, URL, and platform
• Links — profile URL

For each followed account:

• Identity — username, full name
• Status — verified badge, private account flag, Threads account status
• Media — profile picture
• Links — profile URL
• Metadata — position index

How to get your Session ID

This Actor requires a Threads Session ID for authentication. Here's how to get it:

Option 1: Browser Developer Tools

1. Open threads.com in your browser and log in
2. Press F12 to open Developer Tools
3. Go to Application → Cookies → https://www.threads.com
4. Find the cookie named sessionid and copy its value
5. Paste it into the Session ID field in the Actor input

Option 2: Cookie Editor Extension

You can also use a browser extension like Cookie-Editor to quickly view and copy cookies. Simply install the extension, visit threads.com, and search for the sessionid cookie.

Disclaimer: Cookie-Editor is a third-party extension not affiliated with this Actor. As with any browser extension that accesses cookie data, please review its permissions and use at your own discretion.

Important notes

• Get a fresh Session ID before each run. Session IDs can expire at any time — often without warning. For best results, copy a fresh Session ID from your browser immediately before starting each run.

• Use a secondary account. Automated access may cause Threads to flag your account or temporarily restrict it. We strongly recommend using a secondary account rather than your primary one.

• Very large runs may take longer. Processing hundreds of accounts is fully supported, though it may take more time to complete.

Input example

{
"usernames":[
"zuck",
"instagram"
],
"sessionId":"your-session-id-here",
"maxFollowing":0
}

Output example

Profile row (item_type: "profile"):

{
"item_type":"profile",
"sourceUsername":"zuck",
"username":"zuck",
"userId":"314216",
"fullName":"Mark Zuckerberg",
"biography":"...",
"bioUrl":"https://zuck.com",
"bioUrls":["https://zuck.com"],
"profileUrl":"https://www.threads.com/@zuck",
"profilePicUrl":"https://...",
"profilePicHdUrl":"https://...",
"isVerified":true,
"fediverseEnabled":false,
"profileTags":["Tech"],
"podcastName":null,
"podcastUrl":null,
"podcastPlatform":null,
"followerCount":8500000,
"followingCount":null,
"postCount":null,
"isPrivate":false,
"index":null,
"scrapedAt":"2026-02-27T12:00:00.000Z"
}

Following row (item_type: "following"):

{
"item_type":"following",
"sourceUsername":"zuck",
"username":"instagram",
"userId":"25025320",
"fullName":"Instagram",
"profileUrl":"https://www.threads.com/@instagram",
"profilePicUrl":"https://...",
"isVerified":true,
"isPrivate":false,
"hasThreadsAccount":true,
"index":1,
"scrapedAt":"2026-02-27T12:00:00.000Z"
}

Output schema

Each run produces two row types in the same dataset:

¹ Only available on the source user's profile row — not included for individual followed accounts.

² Threads does not make post count publicly available.

³ Field is always present in the row but set to null — position index is only meaningful for following items.

How it works

1. Connects to your Threads account using your Session ID
2. Looks up each username and collects their profile information
3. Collects all accounts they follow — usernames, display names, verification status, and more
4. Keeps going until all accessible following accounts are retrieved or your limit is reached
5. Saves results as they come in — no need to wait for the full run to finish

Tips for best results

• Refresh your Session ID if you see errors. Session IDs can expire at any time. If authentication fails, obtain a fresh one and retry.
• Private accounts are automatically handled. Their profile information will still be collected, but their following list is not accessible. You can identify them by the isPrivate: true field.
• Actual results may be fewer than expected for new accounts. Users with very few following will naturally return fewer results regardless of your limit setting.
• Results may differ from the Threads UI count. The number of accounts returned may be less than the following count shown on the Threads profile — this is a platform-side behavior. All returned accounts are accurate.

Frequently asked questions

Why is a Session ID required?

Threads requires authentication to access following lists. Without a valid session, the Actor cannot retrieve the data.

Is it safe to use my Session ID?

Your Session ID is treated as a secret — it is stored securely by Apify and never exposed in logs or output. That said, we strongly recommend using a secondary Threads account rather than your primary one as a precaution.

How many accounts can I scrape?

In most cases, the Actor collects around 80–90% of a user's following list. Due to how Threads serves data, some accounts may not be returned. The number returned may also be less than the count shown in the Threads profile. All returned accounts are accurate. Set maxFollowing to 0 (the default) to collect as many as possible.

Can I scrape private accounts?

No. Private accounts are not accessible. Their profile information will be collected and returned with isPrivate: true, but their following list will not be available.

What happens if authentication fails?

The Actor will stop and report an authentication error. Obtain a fresh Session ID and try again.

Can I scrape multiple users at once?

Yes. The usernames field accepts up to 10 usernames per run. Each user is processed in sequence.

Integrations

Connect Threads User Following Scraper API with other apps and services using Apify integrations. Export data to Google Sheets, Slack, Zapier, Make, and many more.

Disclaimer

This Actor is intended for learning, research, and personal use. Please use it responsibly and ethically, and ensure your usage complies with Threads' Terms of Service.

Threads may update its platform at any time, which could temporarily affect this Actor's functionality. While we actively maintain compatibility, occasional disruptions are possible.

Using a Session ID involves providing authentication credentials to the Actor. We strongly recommend using a secondary account, as automated access may result in account restrictions or temporary bans. You are solely responsible for how you use this tool and any consequences that may arise from its use.

Threads following scraper, Threads following list, Threads follow list extractor, Threads user following API, Threads account tracker, Threads network analysis, Threads influencer following, Threads social graph, Threads data export, social media scraper, Apify actor, Claude Code, OpenClaw, Gemini, Antigravity, Codex, AI agent tool, LLM data extraction