Threads Scraper

Yes — a public Threads post is public data. Posts, engagement counts and author details are there for anyone who opens the page logged out, and that is all the crawler reads. The finer points live in our guide to the legality of web scraping.

No login required, and nothing to sync. No account, no cookie, no browser extension — your own profile never takes part, so it is never at risk either. Private profiles stay private: the crawler sees only what a logged-out visitor sees.

68 data points per post. The full text and when it went up, likes, replies, reposts, quotes, shares and views, hashtags, mentions, media links and the music behind a clip — plus the author's handle, name, avatar, verified badge, follower count and bio on every single row.

Around 180 posts a minute. A profile's whole back catalogue lands while you are still deciding what to do with it, and a long list of profiles, keywords and tags moves at the same pace as a single one.

Four kinds — a profile, a keyword, a tag or a single post. A profile URL or a bare @handle walks that profile back to its first post, a phrase or a #tag runs a Threads search, a post address returns that post. Mix all four in one list if you like.

Yes — turn on Include Replies and hand it a post address. You get the post plus the replies shown underneath it, usually 20 to 25, each as its own row with its own author and counts. It is off by default, so a post costs one credit until you ask for more.

Yes — set Fetch Since. A window like 24h, 7d or 2w, or a date in the timezone you pick, and anything older is left alone. A profile crawl stops at the first post that misses the cut, so a daily run never re-reads the whole archive.

All of them — left uncapped it goes down to the very first post. Set a maximum per input for a smaller export, or one for the whole run, which also weeds out the posts two keywords both turned up. One credit per post, either way.

Yes — links, type and size for every photo, video, GIF and sticker. The caption rides along, and so do the title and artist of any audio track. The files stay where Threads keeps them and you get direct links, so no saving them one by one.

Just about anywhere you already work. Google Sheets, Make, n8n, Amazon S3, email, webhooks — plus our MCP server, so Claude or ChatGPT can launch a run and read the posts back. CSV, Excel and JSON downloads too. See all integrations.

URL, such as https://www.threads.com/@zuck. Paste thousands at once or upload a CSV; duplicate inputs are skipped. 6 settings shape the run: see them in the playground.

68 data attributes per post, each with its description and an example: see the full list.

No. Duplicates are removed, and you only pay for unique results.

As fresh as your run: each run collects the data from the site at the moment it runs, nothing comes from a stored database.

CSV, Excel or JSON from the dashboard, through the API, or sent after every run to Google Sheets, Amazon S3, an SFTP server, a webhook or by email.

7 days on the free plan, 28 days on paid plans. Then they are deleted. Download or deliver what you want to keep.

Around 180 posts a minute for one squid. Your plan's slots run several squids at the same time.

100.00% of its runs had no incident over the last 90 days (0 incidents, 100% fixed). Every day is on this page.

Our team fixes the scraper: every scraper on lobstr.io is built and maintained by us. How we measure.

Yes, on paid plans: every hour, every day, every weekday or on a custom schedule, in your time zone.

Yes: set the most results per task and per run in the settings. The run stops there and so does the bill.

1 credit per result. The playground shows the price as you pick them.

Yes. The free plan gives 100 credits every month, 100 results with this scraper, with exports capped at 30 rows.

Every month a plan gives credits, which pay for results, and slots, which set how many squids run at the same time. Starter: $20 for 10,000 credits; Pro: $100 for 100,000 credits; Team: $500 for 1,000,000 credits. Upgrades start right away and are prorated; downgrades and cancellations take effect at the end of the cycle.

No. Your credits refresh every month with your plan.

You choose, per squid: pause and pick up where it stopped, or end the run. To keep going, upgrade or reset your billing cycle: your plan renews right away and your credits come back. Auto Billing Reset does it for you when your usage crosses a threshold you set.

Yes: paying yearly takes 20% off every plan.

A monthly plan: within 10 days of the charge, if no credit was used in that period. A yearly plan: within 30 days, in full if no credit was used, otherwise minus one month. Cancel from your billing page, then write to contact@lobstr.io. The details are in the terms of use.

Collecting publicly available data is generally allowed, but you choose what you collect and you are responsible for how you use it. Our terms of use (article 6) ask every user to respect the rights of the sites, not to extract substantial parts of a database, not to access confidential data and to follow personal data law such as the GDPR. This is not legal advice.

When results contain personal data, you are the data controller and lobstr.io, a French company, processes them on your behalf, under our personal data agreement. You need a lawful basis for what you collect, must inform the people concerned and honor their requests.

Results: 7 days on the free plan, 28 days on paid plans, then they are deleted; you can delete them sooner. Your account data: see the privacy notice.

Yes, through the REST API at https://api.lobstr.io/v1, with your key from the dashboard. The playground’s Code tab writes the calls for your settings, in cURL and Python. The documentation has the full reference.

Yes. Add our MCP server, https://mcp.lobstr.io/mcp, to Claude, ChatGPT, Cursor or any MCP client and sign in with lobstr.io. Your agent shows the cost and asks you before a run spends credits. The playground’s Agent tab gives you a prompt.

No. Credits pay for results, not for requests.

Yes. Point a webhook at your server and lobstr.io calls it when a run succeeds or fails.

Yes, per endpoint: 120 requests a minute on squids and runs, 90 on tasks, 2 a second on results. Above that the API answers 429 with a Retry-After header.