🧵 Threads Scraper — Profiles, Posts, Replies & Keyword Search

Threads Scraper extracts public data from Threads (by Meta) — no login, no API key, no Meta developer account. Give it usernames, a search query, or a post URL and it returns profiles, posts, replies, captions, engagement counts (likes, replies, reposts), hashtags, mentions, follower counts, timestamps, and media URLs as structured JSON.

Unlike profile-only Threads actors, this one covers posts, replies, AND keyword search in a single Actor.

Why use Threads Scraper?

• Find and monitor influencers — pull follower counts and engagement to rank accounts.
• Track brand and topic mentions — keyword-search Threads for any term.
• Build datasets for analytics or AI — continuously collect captions, hashtags, and engagement for training or trend analysis.
• Competitive research — watch competitors' posting cadence and reception.
• Lead generation — collect public profile data and bio links at scale.

How it works

Uses a headless Firefox browser (Playwright) to load threads.net and acquire session tokens, then queries the internal GraphQL API directly for efficient bulk collection. Residential proxies are recommended for reliability against Meta's bot detection. Rate limits are respected with automatic backoff.

Input

Field	Type	Description
mode	string	profiles / posts / search / replies
usernames	array	Target usernames (without @)
searchQuery	string	Keyword for search mode
postUrl	string	Full post URL for replies mode
maxPosts	integer	Max posts per user (default 50)
maxReplies	integer	Max replies (default 50)
maxSearchResults	integer	Max search results (default 50)
includeProfile	boolean	Include profile metadata in posts output
proxyConfig	object	Apify proxy config (residential recommended)

Example input

{
  "mode": "posts",
  "usernames": ["zuck", "mark"],
  "maxPosts": 25,
  "includeProfile": true,
  "proxyConfig": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

Output

Each dataset item is a post, profile, or search_result record.

Post record:

{
  "type": "post",
  "postId": "3456789012345678901",
  "username": "zuck",
  "text": "Sharing an update on...",
  "likeCount": 12345,
  "replyCount": 567,
  "repostCount": 89,
  "hashtags": ["meta", "ai"],
  "mentions": ["mark"],
  "timestamp": 1718000000,
  "mediaUrls": ["https://..."],
  "url": "https://www.threads.net/@zuck/post/..."
}

Profile record:

{
  "type": "profile",
  "username": "zuck",
  "fullName": "Mark Zuckerberg",
  "bio": "...",
  "followerCount": 12000000,
  "followingCount": 800,
  "isVerified": true,
  "profilePicUrl": "https://...",
  "url": "https://www.threads.net/@zuck"
}

Pricing

Pay per result at $0.50 per 1,000 items. Example: scraping 25 posts each from 100 profiles = 2,500 items ≈ $1.25 plus Apify platform compute/proxy usage. No subscription, no minimums — you pay only for what you scrape.

FAQ

Is this legal? This Actor accesses only publicly available Threads data. No authentication is bypassed and no login is required. Always comply with applicable data protection laws (GDPR, CCPA) when processing personal data.

Do I need a Meta account or API key? No. The Actor needs neither.

Why residential proxies? Meta applies bot detection; residential proxies materially improve reliability and success rate.