Threads Scraper — Posts, Profiles, Search & Hashtags
Pricing
Pay per usage
Threads Scraper — Posts, Profiles, Search & Hashtags
Scrape Meta Threads: posts, profiles, search, hashtags and replies. Hybrid engine (fast GraphQL + browser fallback). No login needed. Extract text, engagement metrics, media, hashtags and more.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Max Gor
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Scrape Meta Threads without login or API key. Extract posts, profiles, search results, hashtags, and full threads with replies.
Features
- 5 modes in one actor: profiles, posts, threads, search, and hashtags
- Hybrid engine: fast GraphQL API requests with automatic Playwright browser fallback
- No login required — no tokens, no cookies
- Rich data: text, engagement metrics (likes, replies, reposts), media URLs, hashtags, mentions
- Proxy support with Apify Proxy (residential recommended)
Input
| Parameter | Type | Description |
|---|---|---|
mode | string | profiles, posts, thread, search, or hashtags |
profiles | string[] | Usernames or profile URLs (for profiles and posts modes) |
postUrls | string[] | Post URLs (for thread mode) |
searchQueries | string[] | Search keywords (for search mode) |
hashtags | string[] | Hashtag strings (for hashtags mode) |
maxResults | number | Max results per query/profile (default: 50) |
proxyConfiguration | object | Proxy settings |
Example: Scrape user posts
{"mode": "posts","profiles": ["zuck", "instagram"],"maxResults": 20}
Example: Search by keyword
{"mode": "search","searchQueries": ["artificial intelligence", "web scraping"],"maxResults": 50}
Example: Get a thread with replies
{"mode": "thread","postUrls": ["https://www.threads.net/t/C8H5FiCtESk"]}
Example: Hashtag tracking
{"mode": "hashtags","hashtags": ["tech", "ai"],"maxResults": 100}
Output
Posts
| Field | Type | Description |
|---|---|---|
id | string | Threads post ID |
code | string | Short code for URL |
url | string | Direct link to the post |
text | string | Post content |
username | string | Author's username |
userVerified | boolean | Verified account badge |
publishedAt | string | ISO 8601 timestamp |
likeCount | number | Number of likes |
replyCount | number | Number of replies |
repostCount | number | Number of reposts |
images | string[] | Image URLs |
videos | string[] | Video URLs |
hashtags | string[] | Extracted hashtags |
mentions | string[] | Extracted @mentions |
isReply | boolean | Whether this is a reply |
Profiles
| Field | Type | Description |
|---|---|---|
username | string | Threads handle |
fullName | string | Display name |
bio | string | Profile bio |
profilePicUrl | string | Avatar URL |
followerCount | number | Followers count |
followingCount | number | Following count |
isVerified | boolean | Verified badge |
isPrivate | boolean | Private account |
externalUrl | string | Website link |
Use Cases
| Who | What |
|---|---|
| Social media managers | Track brand mentions, monitor competitor content |
| Marketers | Analyze trending hashtags, measure engagement |
| Researchers | Collect public opinion data, study viral content |
| Journalists | Monitor public figures, track breaking stories |
| Developers | Feed Threads data into apps, dashboards, analytics |
| Influencers | Track engagement metrics, find trending topics |
How it works
- GraphQL layer (fast, lightweight): Sends direct API requests to Threads' internal GraphQL endpoint — same requests the browser makes. No authentication needed. Works for profiles, posts, and threads.
- Playwright fallback (reliable): If GraphQL is blocked (403/429), automatically launches a headless browser. Also used for search and hashtag modes which don't have public GraphQL endpoints.
- Anti-bot resilience: User-Agent rotation, request delays, exponential backoff, and Apify Proxy integration.
Pricing
This actor uses a pay-per-result model:
| Results | Cost |
|---|---|
| 1,000 | ~$1.00 |
| 10,000 | ~$10.00 |
| 100,000 | ~$100.00 |
Platform compute costs (memory + time) are additional. Recommended: 1 GB memory for most runs.
Tips
- Use residential proxies for best reliability (Apify RESIDENTIAL group)
searchandhashtagsmodes require a browser, so they use more memory and time- Keep
maxResultsreasonable (50-200) for faster runs - For monitoring, run the actor on a schedule (e.g., hourly hashtag tracking)
FAQ
Q: Do I need a Threads account? A: No. All data is scraped from public pages without login.
Q: What proxies should I use? A: Residential proxies work best. Set Apify Proxy with RESIDENTIAL group in the proxy configuration.
Q: Why are some posts missing text? A: Image-only or video-only posts may have no text content. The media URLs are still extracted.
Q: Can I monitor a hashtag over time? A: Yes! Schedule this actor to run hourly/daily with the same hashtag. Compare datasets to track trends.
Q: What's the difference between GraphQL and Playwright modes? A: GraphQL is faster and cheaper but may get blocked without proxies. Playwright is slower but more reliable. The actor switches automatically.
Integrations
- Google Sheets — export directly from Apify
- Webhooks — trigger on completion
- API — fetch results programmatically
- Zapier / Make — automate workflows
- Slack / Email — get notified on new results
Limits
- Threads may rate-limit or block requests — proxies help significantly
- Private profiles return limited data
- Search results depend on Threads' ranking algorithm
- Media URLs are temporary (CDN links may expire)