Threads Replies Scraper API
Pricing
from $1.00 / 1,000 results
Scrape Threads replies (comments): reply text, likes, reposts, author details and media, with nested replies on request. Requires a Threads Session ID.
One Threads post link per line, such as https://www.threads.com/@username/post/CODE. threads.net links, share links (threads.com/share/…) and short links (threads.com/t/…) work too. A link to a reply collects the replies underneath that reply. A run collects up to 50 posts, and each share or short link counts as one of them; a longer list stops the run as it starts, so split it across runs.
Paste the sessionid cookie from a Threads account you are signed in to. In your browser: Developer Tools → Application (Storage in Firefox and Safari) → Cookies → threads.com → sessionid. Full walkthrough in the README. We recommend a secondary account.
Stop at this many replies per post, nested replies included; the post's own row is extra. Set 0, or leave it out of an API call, to collect as many replies as Threads lists, which can be fewer than the number the post shows.
Top lists replies in the order Threads ranks them, as Threads shows them by default; on a busy post, Threads' ranking can end before the last replies, which follow it. Recent lists the newest replies first.
Also collect replies to replies, around five levels down. Nested replies count toward Max Replies Per Post, and that limit can fill before they are reached, so set it to 0 when you want them. With this off, some nested replies can still appear: the answers Threads shows directly under a reply.
