π§΅ Threads Replies Scraper
Pricing
from $4.99 / 1,000 results
π§΅ Threads Replies Scraper
π§΅ Threads Replies Scraper helps you extract replies, threads, and engagement data from Threads fast. π Perfect for social media research, brand monitoring, and lead insightsβsave time and turn conversations into actionable data. πβ¨
Pricing
from $4.99 / 1,000 results
Rating
0.0
(0)
Developer
Scraper Engine
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
5 days ago
Last modified
Categories
Share
Extract the original post plus all its replies β including nested sub-replies β from any public Threads post, as clean, structured JSON/CSV/Excel. Perfect for social listening, sentiment analysis, audience research, and building Threads datasets.
β¨ Why Choose This Actor?
- π§΅ Full conversation capture β original post and its reply tree, not just top-level comments.
- π¬ Nested replies β optionally follow replies-to-replies inside the same thread.
- π‘οΈ Self-healing proxy ladder β starts direct, auto-escalates to datacenter, then residential if Threads pushes back. No manual tuning.
- πΎ Live results β records stream into your dataset as they are scraped; a stopped run still keeps everything collected so far.
- π Rich output β likes, replies, reposts, quotes, views, media URLs, mentions, hashtags, verification, and more.
- ποΈ Tidy views β Overview, Original Posts, and Replies tables out of the box.
π Key Features
| Feature | Description |
|---|---|
| Bulk input | Scrape many post URLs in one run |
| Reply cap | Collect 10β50 replies per post |
| Nested sub-replies | Toggle replies-to-commenters on/off |
| Media | Image / video / carousel / GIF URLs |
| Entities | Mentions, hashtags, and links parsed out |
| Engagement | Likes, replies, reposts, quotes, shares, views |
| Proxy fallback | Direct β Datacenter β Residential (sticky) |
π₯ Input
| Field | Type | Required | Description |
|---|---|---|---|
post_urls | array | β | One or more Threads post URLs (bulk supported). |
sessionid | string | β | A logged-in Threads/Instagram sessionid cookie. Threads returns no replies without it. |
max_replies | integer | β | Replies per post, 10β50 (default 50). |
include_nested_replies | boolean | β | Also collect replies-to-commenters (default false). |
proxyConfiguration | object | β | Apify Proxy preferences. Starts direct, escalates automatically. |
Example input
{"post_urls": [{ "url": "https://www.threads.com/@zuck/post/DTa3-B1EbTp" }],"sessionid": "PASTE_YOUR_SESSIONID_COOKIE_HERE","max_replies": 50,"include_nested_replies": false,"proxyConfiguration": { "useApifyProxy": true }}
πͺ How to get your sessionid
- Log in to threads.com in your browser.
- Open DevTools β Application (Chrome) / Storage (Firefox) β Cookies β
https://www.threads.com. - Copy the value of the
sessionidcookie and paste it into the input.
π€ Output
Each run produces two record types in the dataset.
Original post (item_type: "original_post"):
{"post_code": "DTa3-B1EbTp","post_url": "https://www.threads.com/@zuck/post/DTa3-B1EbTp","author_username": "zuck","author_display_name": "Mark Zuckerberg","author_is_verified": true,"text_content": "Today we're establishing a new top-level initiativeβ¦","like_count": 2926,"reply_count": 995,"repost_count": 150,"quote_count": 40,"share_count": 241,"view_count": 505453,"has_media": false,"created_at": "2026-01-12T18:00:30.000Z","item_type": "original_post"}
Reply (item_type: "reply"):
{"reply_id": "DTa4RWwDy3-","author_username": "jasondwalters","author_display_name": "Jason Walters","text_content": "Oh wow. How many elections can you interfere with now simultaneously?","reply_to_username": "zuck","like_count": 181,"created_at": "2026-01-12T18:03:08.000Z","reply_url": "https://www.threads.com/@jasondwalters/post/DTa4RWwDy3-","item_type": "reply"}
π How to Use (Apify Console)
- Log in at console.apify.com β Actors.
- Open Threads Replies Scraper.
- Paste your post URLs and your
sessionidcookie, setmax_replies, choose proxy preferences. - Click Start.
- Watch the live log as posts and replies stream in.
- Open the Output / Storage tab to view the Overview, Original Posts, and Replies tables.
- Export to JSON / CSV / Excel.
π€ Use via API
curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/run-sync-get-dataset-items?token=$APIFY_TOKEN" \-H "Content-Type: application/json" \-d '{"post_urls": [{ "url": "https://www.threads.com/@zuck/post/DTa3-B1EbTp" }],"sessionid": "PASTE_YOUR_SESSIONID_COOKIE_HERE","max_replies": 50}'
π‘ Best Use Cases
- Social listening & brand monitoring on Threads
- Sentiment and community analysis on viral posts
- Researching how conversations and sub-threads evolve
- Building Threads reply datasets for ML / analytics
π³ Pricing
This Actor uses the pay-per-event model: you are billed per record collected (the original post and each reply). Lowering max_replies reduces cost. Platform compute and proxy usage follow standard Apify rules.
β FAQ
Why is a sessionid required? Threads only returns the reply tree to authenticated sessions. Without a valid sessionid the API responds with an execution error and no replies.
How many replies can I get? Up to 50 per post in one run, controlled by max_replies. Threads paginates the reply tree; the Actor follows it until the cap or the end is reached.
What if Threads blocks me? The Actor automatically escalates from direct connection to a datacenter proxy, then to a residential proxy, and sticks with the working tier for the rest of the run.
Do I get sub-replies? Only if you enable include_nested_replies. By default just first-level replies are collected.
βοΈ Notes & Compliance
- Data is collected only from publicly available Threads posts.
- You are responsible for complying with Threads' Terms of Service and applicable laws (GDPR, CCPA, etc.).
- Use your own account's
sessionidand respect reasonable rate limits.
π Support & Feedback
Found a bug or want a new field? Open an issue on the Actor's Issues tab in the Apify Console.