# Threads Replies Scraper - Comments & Reply Threads, No Login (`alom/threads-replies-scraper`) Actor Scrape replies (comments) under any Threads post without login: text, author, likes, date, whole nested reply threads and which replies the author liked. Top or newest first, about the first 900 per post. Or every reply an account wrote. From $1.50 per 1,000. - **URL**: https://apify.com/alom/threads-replies-scraper.md - **Developed by:** [Alom Dev](https://apify.com/alom) (community) - **Categories:** Social media, Lead generation - **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: 5.00 out of 5 stars ## Pricing from $1.50 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Threads Replies Scraper: Comments & Reply Threads, No Login Get the **replies (comments) under any Threads post** as a table: paste post URLs and you get **one row per reply** with the text, author, likes, reply count, date, media and links, the reply it answers, and whether the post author liked it. You can also paste usernames to get **every reply an account wrote**. - **No login needed.** It reads what a logged-out visitor of threads.com sees. No account of yours is involved. - **Whole reply threads.** Threads shows only one answer under a reply. This Actor opens each thread and reads it in full, every row linked to the reply it answers (`parentPostId`). Or turn threads off to get only direct replies. - **Top or newest first.** Newest first follows a post as the reactions come in. - **Only new replies on a schedule.** Monitoring mode skips replies an earlier run returned, and you don't pay for them. - **You pay for replies only.** The post itself is not a row unless you ask for it. - Export to CSV, Excel or JSON, or pull results through the Apify API. This Actor is a focused version of the [Threads Scraper](https://apify.com/alom/threads-scraper) (same code, same prices). Use the Threads Scraper if you also need a profile's posts, reposts or a keyword search. ### What can you use it for? - **Reactions to an announcement:** read what people answer under a launch post, a statement or an ad. - **Customer feedback:** collect the replies under your own posts and sort them by likes. - **Community research:** see what an account says in conversations, which is often more telling than its posts. - **Datasets for analysis and AI:** real reply threads with timestamps, authors and engagement counts. ### Input | Field | What it does | |---|---| | `postUrls` | Threads post URLs, e.g. `https://www.threads.com/@mosseri/post/DdUI1VfG_42` (threads.net works too). | | `usernames` | Optional. For each account: the replies it wrote (its Replies tab), each with the post it answered. | | `maxReplies` | Max replies per post and per account. Default 100. | | `repliesSort` | `top` (Threads' order) or `recent` (newest first). Left empty: top, or newest first when monitoring is on. | | `includeNestedReplies` | The whole thread under each reply. Default on. Off = only direct replies to the post. | | `maxNestedReplies` | Max replies under one reply. Default 20, so one busy thread cannot use up `maxReplies`. | | `includeOriginalPost` | Also return the post itself as a row. Default off. | | `postedAfter` | Only replies after a date, e.g. `2026-10-01` or `7 days`. | | `minLikes` | Keep only replies with at least this many likes. | | `includeViews` | Fill `viewCount` (the number Threads shows under a reply, e.g. "2.2K views") on every reply. One extra request per reply, about 1.5 s each, not charged. Default off. | | `onlyNewSinceLastRun` + `monitorName` | Skip replies an earlier run with the same monitor name returned. | ```json { "postUrls": ["https://www.threads.com/@mosseri/post/DdUI1VfG_42"], "maxReplies": 300, "repliesSort": "top" } ``` ```json { "usernames": ["mosseri"], "maxReplies": 50 } ``` ```json { "postUrls": ["https://www.threads.com/@mosseri/post/DdUI1VfG_42"], "onlyNewSinceLastRun": true, "monitorName": "launch-post" } ``` #### Switching from another Threads replies scraper? Keep your input. These field names are accepted as they are: `post_urls` or `postUrls` (strings or `{ "url": ... }` objects), `max_replies` / `maxRepliesPerPost`, `include_nested_replies` / `includeNestedReplies` / `includeChildReplies`, and `sortOrder` (`top` or `recent`). No session id or cookie is needed. ### Output example ```json { "type": "reply", "postId": "3731234567890123456", "code": "Dd1Pxa2ExAm", "url": "https://www.threads.com/@example_user/post/Dd1Pxa2ExAm", "text": "This is the part I was waiting for. When does it roll out in Europe?", "username": "example_user", "fullName": "Example User", "isVerified": false, "likeCount": 214, "replyCount": 3, "repostCount": 1, "quoteCount": 0, "mediaType": "text", "media": [], "isReply": true, "replyToUsername": "zuck", "parentPostId": "3730000000000000001", "rootPostId": "3730000000000000001", "isLikedByAuthor": true, "date": "2026-09-28T15:04:11.000Z", "source": "post:Dd1MqfcG0aH", "scrapedAt": "2026-10-12T09:00:00.000Z" } ``` (The reply above is made up; the fields are what you get.) `rootPostId` is the post whose replies you asked for. `parentPostId` is the row this reply answers: the post itself for a direct reply, another reply inside a thread. Rows from `usernames` also carry `repliedToPost` (the post that was answered) and `sourceTab: "replies"`. Values Threads doesn't show are `null`, never a made-up `0`. ### How much does it cost? The same prices as the Threads Scraper: **from $1.50 per 1,000 replies**, plus $0.005 per run. One result = one reply row. Platform usage (compute, proxy) is included. | Apify plan | Price per 1,000 replies | |---|---| | Free | $2.50 | | Starter (Bronze) | $2.00 | | Scale (Silver) | $1.75 | | Business (Gold) and above | $1.50 | 500 replies under a post cost **$1.25** on the Free plan and **$0.75** on Business. You pay only for rows you receive: replies a monitor already returned, replies outside your date window and posts that don't exist are free. ### Monitoring (only new replies) Turn on **"Only new replies since my last run"**, give it a name (e.g. `launch-post`) and schedule the run in Apify Console. Each run reads the replies newest first and stops at the first one an earlier run delivered, so an hourly check of a quiet post costs almost nothing. ### Limitations - **Roughly the first 1,000 direct replies per post.** That is how far Threads lets a logged-out visitor page: a post with about 6,600 replies gave 908 direct replies in our test. - **Threads are read up to 6 levels deep** and up to `maxNestedReplies` rows per direct reply (default 20). In our test a post gave 245 direct replies and 79 replies inside threads, and 32 of its 34 threads were complete. - **A reply's counter can be slightly higher than the rows you get.** Some replies are not shown to logged-out visitors (in the same test, 64 of 66 counted replies came back). - **Speed:** about 250 replies a minute. - **Monitoring follows new direct replies.** Threads under replies an earlier run already delivered are not read again. - **No view counts.** Threads doesn't show them to logged-out visitors. - A post URL that doesn't exist fails that input only (it is named in the run's status message); the rest of the run is delivered. ### FAQ **Do I need a Threads or Instagram account?** No. Nothing is logged in, so there is nothing to ban. **Is "replies" the same as "comments"?** Yes. Threads calls the comments under a post replies. **Can I get the replies to a reply?** Yes, whole threads are included by default. Each row's `parentPostId` tells you which reply it answers. `isLikedByAuthor` marks the replies the post's author liked. **Is it legal?** The Actor collects only what Threads shows publicly without login. Replies are personal data: check that your use has a lawful basis (GDPR and similar laws) before you store or process them. ### More scrapers from the same developer - [Threads Scraper](https://apify.com/alom/threads-scraper): posts, profiles, replies, reposts, keyword and hashtag search, account search - [Threads Account Finder](https://apify.com/alom/threads-lead-finder): Threads accounts by keyword with followers, bio links and the contacts they list - [Threads Hashtag & Keyword Monitor](https://apify.com/alom/threads-keyword-monitor): only the new posts for your keywords and #hashtags, for scheduled runs - [Google Trends API & Scraper](https://apify.com/alom/google-trends-scraper): interest over time, regions, related queries and Trending Now, a pytrends alternative - [YouTube Scraper](https://apify.com/alom/youtube-scraper): videos, channels, Shorts, comments, subtitles and community posts without the API quota - [YouTube Comments Scraper](https://apify.com/alom/youtube-comments-scraper): comments and replies of any YouTube video or Short - [YouTube Channel Scraper](https://apify.com/alom/youtube-channel-scraper): every video of a channel with views, likes, dates and channel stats - [YouTube Shorts Scraper](https://apify.com/alom/youtube-shorts-scraper): Shorts by channel or keyword with views and likes - [Bilibili Scraper](https://apify.com/alom/bilibili-scraper): videos, creators, full comment threads and danmaku from Bē«™, no login - [Google Hotels Scraper](https://apify.com/alom/google-hotels-scraper): hotel prices from every booking site across dates, room rates and reviews - [Google Flights Scraper](https://apify.com/alom/google-flights-scraper): flight prices, airlines, layovers and a cheapest-date calendar for any route - [Google Ads Transparency Scraper](https://apify.com/alom/google-ads-transparency-scraper): every Google ad a competitor runs, with the real ad copy ### Feedback Missing a field, found a bug, or need a feature? Open an issue in the **Issues** tab and I'll take a look. If this Actor saved you time, a short review on the Store page helps other people find it. # Actor input Schema ## `postUrls` (type: `array`): Threads posts whose replies you want, e.g. https://www.threads.com/@mosseri/post/DdUI1VfG_42 (threads.net links work too). You get one row per reply. ## `usernames` (type: `array`): Optional. For each account you get the replies it wrote (its Replies tab), each with the post it answered. E.g. mosseri, @nasa or a profile URL. ## `maxReplies` (type: `integer`): Upper limit for each post URL and each username. Threads shows logged-out visitors roughly the first 1,000 replies of a post. ## `repliesSort` (type: `string`): Top is the order Threads shows. Newest first is what you want when following a post over time. Left empty: Top, or Newest first when monitoring is on. ## `includeNestedReplies` (type: `boolean`): On: the whole thread under each reply, every row linked to the reply it answers (parentPostId). Threads shows only one answer under a reply, so each thread is opened and read in full. Off: only direct replies to the post. ## `maxNestedReplies` (type: `integer`): Cap for one reply thread, so a single busy thread cannot use up Max replies per post. 0 = direct replies only. ## `includeOriginalPost` (type: `boolean`): Adds one row for the post (and the author's own continuation of it) before its replies. Off by default, so you only pay for replies. ## `postedAfter` (type: `string`): Date (UTC), ISO timestamp or relative like 7 days. Older replies are skipped (not charged). ## `minLikes` (type: `integer`): Keep only replies with at least this many likes. Leave empty for no limit. ## `includeViews` (type: `boolean`): Fill viewCount (the number Threads shows under a reply, e.g. 2.2K views) on every reply. Each count is read from the reply's own page: one extra request per reply, so the run takes longer. Not charged extra. ## `onlyNewSinceLastRun` (type: `boolean`): Skip replies an earlier run with the same monitor name already returned (you are not charged for them). Pair with a Schedule in Apify Console to follow a post. ## `monitorName` (type: `string`): Each name keeps its own memory of delivered replies, e.g. launch-post. Use a new name to start from scratch. ## `maxConcurrency` (type: `integer`): Posts and accounts processed in parallel. ## `proxyConfiguration` (type: `object`): The default Apify datacenter proxy works and is included in the price. If Threads starts blocking it, the run switches to residential proxies by itself (logged). ## Actor input object example ```json { "postUrls": [ "https://www.threads.com/@mosseri/post/DdUI1VfG_42" ], "maxReplies": 50, "includeNestedReplies": true, "maxNestedReplies": 20, "includeOriginalPost": false, "includeViews": false, "onlyNewSinceLastRun": false, "monitorName": "default", "maxConcurrency": 3, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "postUrls": [ "https://www.threads.com/@mosseri/post/DdUI1VfG_42" ], "maxReplies": 50 }; // Run the Actor and wait for it to finish const run = await client.actor("alom/threads-replies-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`šŸ’¾ Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // šŸ“š Want to learn more šŸ“–? Go to ā†’ https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "postUrls": ["https://www.threads.com/@mosseri/post/DdUI1VfG_42"], "maxReplies": 50, } # Run the Actor and wait for it to finish run = client.actor("alom/threads-replies-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"šŸ’¾ Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # šŸ“š Want to learn more šŸ“–? Go to ā†’ https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "postUrls": [ "https://www.threads.com/@mosseri/post/DdUI1VfG_42" ], "maxReplies": 50 }' | apify call alom/threads-replies-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,alom/threads-replies-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/t7lgukaOWv5PaDRaX/builds/oAk3rJJ8oEfvOeVmq/openapi.json