π§΅β¨ Threads User Followers Scraper
Pricing
from $4.99 / 1,000 results
π§΅β¨ Threads User Followers Scraper
π§΅β¨ Threads User Followers Scraper that pulls followers & following, finds mutuals, and maps relationships. π Export CSV/JSON, schedule runs, track changes. Perfect for marketing, competitor research & influencer outreach.
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
API Empire
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
10 days ago
Last modified
Categories
Share
Threads User Followers Scraper
Apify Actor that collects Threads follower records for one or more profiles, using the same GraphQL + HTML token strategy as a local Python workflow (extract_followers + profile HTML + JS bundle doc_id extraction).
Features
- Bulk input: multiple profile URLs or
@usernames - Session-based: requires a valid
sessionidcookie (paste assessionIdinput; fromthreads.com/ Instagram when logged in) - Proxy ladder: starts with no proxy; on failure uses Apify datacenter, then residential (up to 3 attempts); after residential succeeds, stays on residential for the rest of the run
- Live dataset output: each follower row is pushed as it is discovered
- Same output shape as the normalized JSON from
node_to_record(source, target_username, user_id, pk, username, full_name, flags, profile_url, etc.)
Input
| Field | Type | Description |
|---|---|---|
urls | array | Profile URLs or usernames |
sessionId | string (secret) | Value of the sessionid cookie (browser DevTools β Application β Cookies β threads.com or instagram.com) |
proxyConfiguration | object | Optional; merged into Apify proxy configuration for DC/residential fallbacks |
maxFollowers | integer | Max unique followers per profile (default 200) |
Pacing and GraphQL batching match the original script internally (~0.35s between rounds, first=50, stop after 10 consecutive rounds with no new unique followers).
Example:
{"urls": ["https://www.threads.com/@zuck"],"sessionId": "YOUR_SESSIONID","maxFollowers": 200}
Output
Each dataset item matches the scraper record shape, for example:
{"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"}
Local run
cd Threads-User-Followers-Scraperpip install -r requirements.txt
- Set
APIFY_TOKENin the environment so Apify Proxy fallbacks can obtain a proxy password when direct access fails. - Run
apify runwith the Apify CLI, orpython -m srcwith optional project-rootINPUT.json(only ifActor.get_input()is empty β e.g. local testing).
Legal
Only scrape data you are allowed to access. You are responsible for complying with Threads/Meta terms and applicable laws.