Threads Scraper — Search, Profiles, Posts & Replies (No Login)

Scrape public Threads posts by keyword, profile or post URL — including replies — without a Threads account, cookies or API key.

Built for reliability: every search term, profile and post gets a clear status in the run report, so you never get an empty dataset without knowing why. And you only pay for results that are delivered.

What you can do

• 🔎 Search Threads by keyword, phrase or hashtag (top or recent)
• 👤 Scrape profiles: latest posts plus profile details (bio, followers, verification, links)
• 💬 Scrape posts and their replies from any post URL
• 🧵 Go beyond the logged-out limit: turn on Also collect replies to open each post found and collect its replies
• 🔔 Monitor a brand or topic: only new posts mode skips everything earlier runs already returned — schedule it daily and get fresh mentions only
• 📅 Filter by date: keep only posts published after a given day

Why this Threads scraper

	This Actor
Login, cookies or API key	Not needed
Status per search / profile / post	✅ ok, not_found, blocked, login_wall
Pay only for delivered results	✅
Retries with fresh sessions on soft blocks	✅
Monitoring (new posts only)	✅
Replies with parent / reply labels	✅

Input example

{
  "searchTerms": ["nike", "#ai"],
  "usernames": ["zuck"],
  "postUrls": ["https://www.threads.com/@zuck/post/C8abc123"],
  "sort": "recent",
  "includeReplies": true,
  "maxPostsPerTarget": 50,
  "maxResults": 300
}

Output example

{
  "postId": "3456789012345678901",
  "code": "C8abc123",
  "url": "https://www.threads.com/@zuck/post/C8abc123",
  "text": "Big update today #ai",
  "createdAt": "2026-10-20T14:03:11.000Z",
  "likeCount": 12873,
  "replyCount": 941,
  "repostCount": 312,
  "quoteCount": 40,
  "isReply": false,
  "hashtags": ["ai"],
  "mentions": [],
  "images": ["https://..."],
  "videos": [],
  "author": { "username": "zuck", "fullName": "Mark Zuckerberg", "isVerified": true },
  "relation": "result",
  "source": { "type": "search", "value": "#ai" },
  "scrapedAt": "2026-10-21T08:00:00.000Z"
}

relation tells you what each row is: result (search), post (profile post or the requested post), parent (the post it answers) or reply.

The run report (key-value store, record OUTPUT) lists every target with its status and counts, plus the profile details collected.

Good to know

• Threads shows logged-out visitors only part of its content (about 20–25 posts per search or profile). Turn on Also collect replies to collect much more around the same topic.
• Residential proxies are used by default: Threads blocks datacenter IPs.
• Only public data is collected. Use the data in line with applicable laws (including GDPR) and Threads' terms.

Use cases

Brand and competitor monitoring · social listening · trend and hashtag research · influencer discovery · sentiment analysis · datasets for AI and research.

Pricing

Pay per result: you are charged for each post delivered to your dataset — not for failed pages, skipped duplicates or posts filtered out by date.