Threads Scraper — Posts, Profiles & Search, No Login
Pricing
from $8.00 / 1,000 threads results
Threads Scraper — Posts, Profiles & Search, No Login
Scrape public Threads posts, profiles, keyword search and user search: text, likes, replies, reposts, media and followers. No login. USD 10 per 1,000 results.
Pricing
from $8.00 / 1,000 threads results
Rating
0.0
(0)
Developer
Muhammad Afzal
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
18 days ago
Last modified
Categories
Features
Share
Threads Scraper collects public Threads data in five modes (user posts, profile details, single posts with replies, keyword search and user search) and returns post text, publish time, likes, replies, reposts, quotes, shares, media URLs, hashtags, mentions, follower counts and bio links. It is built for social listening, brand monitoring and creator research teams, and costs USD 10 per 1,000 results on the FREE tier plus a USD 0.02 start fee.
No Threads login, cookies or Meta developer app are needed. You give usernames, post URLs or search terms; you get one clean JSON record per post or profile.
What data does the Threads Scraper return?
Every record has type, id, url, username, source and scrapedAt. The other fields depend on whether the record is a post, a reply or a profile:
| Field | Applies to | What it contains |
|---|---|---|
type | all | post, reply or profile |
id | all | Stable Threads ID, used for deduplication |
url | all | Public threads.com post or profile URL |
username | all | Threads username |
fullName | all | Display name, or null |
verified | all | Verification badge, or null |
text | posts, replies | Post text |
publishedAt | posts, replies | Publish time in UTC (ISO 8601), or null |
likes, replies, reposts, quotes, shares | posts, replies | Public engagement counts, or null |
media | posts, replies | Image and video URLs as { "type", "url" } |
hashtags, mentions | posts, replies | Tags and @mentions found in the text |
parentUrl | replies | URL of the post the reply belongs to |
biography | profiles | Profile bio, or null |
followers | profiles | Follower count, or null |
isPrivate | profiles | Whether the account is private, or null |
profilePictureUrl | profiles | Profile picture URL, or null |
bioLinks | profiles | Links listed on the profile |
source | all | The mode and input target that produced the record |
scrapedAt | all | Collection time in UTC |
Missing values stay null. Profiles found through user search can have fewer filled fields than profiles fetched directly.
When should you use it, and when not?
Use it when you:
- monitor what a brand, executive or creator posted on Threads recently, with engagement counts;
- collect profile details (bio, followers, verification, bio links) for a list of accounts;
- pull public conversations about a keyword, optionally limited to a date range;
- read one post and its visible replies for engagement analysis.
Do not use it when you:
- need an account's full posting history. Each target returns the recent public window only; there is no cursor pagination.
- need follower or following lists, hashtag feeds or private content. These are not supported.
- need to download images or videos. You get media URLs, which can expire.
- need creator link pages. Use Linktree Scraper.
How do I scrape Threads posts, profiles and search results?
Pick a mode and fill the matching input list. The same targets returned data in cloud test runs:
{ "mode": "posts", "handles": ["zuck"], "maxResults": 20, "maxResultsPerTarget": 20, "maxRequests": 10 }
{ "mode": "search", "queries": ["technology"], "maxResults": 10, "maxRequests": 2 }
{ "mode": "post", "postUrls": ["https://www.threads.com/@zuck/post/Ddt7cL5EfUG"], "includeReplies": true, "maxResults": 10 }
| Mode | Input list | Returns |
|---|---|---|
posts (default) | handles | Recent public posts of each user |
profiles | handles | One profile record per user |
post | postUrls | The post, plus visible replies when includeReplies is true |
search | queries | Posts matching each keyword; startDate and endDate (YYYY-MM-DD) narrow the dates |
users | queries | Profiles matching each search term |
Limits: up to 20 handles, post URLs or queries per run. maxResults caps the whole run (1–500, default 20), maxResultsPerTarget caps each target (1–100, default 20), and maxRequests caps data requests including retries (1–20, default 10). Handles accept zuck, @zuck or a threads.com or threads.net profile URL; duplicates are merged.
What does the output look like?
Two records from the default run on 2026-10-26, with the media URL shortened:
[{"type": "post","id": "3996155940894885511","url": "https://www.threads.com/@zuck/post/Dd1MqfcG0aH","username": "zuck","fullName": null,"text": "We believe superintelligence will create significant new opportunities for all people and businesses. ...","publishedAt": "2026-09-28T12:35:32.000Z","likes": 2754,"replies": 2668,"reposts": 173,"quotes": 160,"shares": 180,"verified": true,"media": [],"hashtags": [],"mentions": [],"parentUrl": null,"source": { "mode": "posts", "target": "zuck" },"scrapedAt": "2026-10-26T07:45:03.878Z"},{"type": "post","id": "4006376160339141718","url": "https://www.threads.com/@zuck/post/DeZgeQhm6RW","username": "zuck","fullName": null,"text": "Muse ordered me 🍉 how thoughtful!","publishedAt": "2026-10-12T15:01:17.000Z","likes": 1605,"replies": 497,"reposts": 112,"quotes": 38,"shares": 72,"verified": true,"media": [{ "type": "image", "url": "https://scontent-ord5-2.cdninstagram.com/v/t51.82787-15/...webp" }],"hashtags": [],"mentions": [],"parentUrl": null,"source": { "mode": "posts", "target": "zuck" },"scrapedAt": "2026-10-26T07:45:03.878Z"}]
The OUTPUT key-value record holds the run status (DATA, PARTIAL, EMPTY, LIMIT_REACHED, FAILED or REJECTED), delivered count, request count, warnings, stop reason, effective limit and charged event counts.
Pricing: how much does the Threads Scraper cost?
You pay a start fee per run and a fee per unique record saved. Apify platform usage is included.
| Event | FREE | BRONZE | SILVER | GOLD | PLATINUM | DIAMOND |
|---|---|---|---|---|---|---|
| Actor start, per started GB of allocated memory | $0.02 | $0.0195 | $0.019 | $0.016 | $0.016 | $0.016 |
| Threads result (primary event) | $0.01 | $0.00975 | $0.0095 | $0.008 | $0.008 | $0.008 |
| Per 1,000 results | $10 | $9.75 | $9.50 | $8 | $8 | $8 |
Worked totals at the default 128 MB memory (one start event):
- The default run on 2026-10-26 saved 15 posts on the FREE tier: $0.02 + 15 × $0.01 = $0.17.
- 100 results on the GOLD tier: $0.016 + 100 × $0.008 = $0.816.
Empty, rejected and failed targets are not charged; only the start fee applies when nothing is saved. Duplicates are skipped before saving, so you never pay twice for the same post or profile.
How reliable is it, and what are the limits?
- The default run on 2026-10-26 returned 15 posts in about 8 seconds using one data request.
- Each target gets one request with a 45-second timeout and at most one retry. The run stops new work after about 170 seconds.
- After two failed targets in a row, the run stops and keeps everything already saved.
- Recent windows only: a user's posts and a keyword search return what is currently exposed publicly, not an archive. Counts vary by account and term.
- Related posts and the author's continuation posts on a post page are not included.
Use it from an AI assistant
Threads Scraper works from Claude, ChatGPT, Cursor or any MCP client through Apify's MCP server. Add https://mcp.apify.com/?tools=muhammadafzal/threads-posts-profiles-search-scraper as a server in your client and the assistant can run it directly. Example prompt: "Get the 20 most recent public Threads posts from @zuck and tell me which ones got the most replies."
API examples
JavaScript (npm install apify-client):
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('muhammadafzal/threads-posts-profiles-search-scraper').call({mode: 'profiles',handles: ['zuck'],maxResults: 1,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items[0].followers, items[0].bioLinks);
Python (pip install apify-client):
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("muhammadafzal/threads-posts-profiles-search-scraper").call(run_input={"mode": "search", "queries": ["technology"], "maxResults": 10})for item in client.dataset(run.default_dataset_id).iterate_items():print(item["username"], item["likes"], item["text"][:80])
FAQ
Do I need a Threads account or cookies?
No. The Actor handles data access and returns public data only. You never enter Threads or Instagram credentials.
Is this a Threads API alternative?
Yes, for public data. You get posts, profiles and search results as JSON through the Apify API without creating a Meta developer app or going through OAuth review.
How many posts can I get per account?
The recent public window for that account, which varied by account in testing; the default run returned 15 posts for @zuck. There is no pagination to older posts.
Can I search Threads by keyword and date?
Yes. Use mode: "search" with queries, and optionally startDate and endDate in YYYY-MM-DD format. Dates apply only to keyword search.
Does it return replies?
Yes, in post mode with includeReplies: true. You get the replies visible with that post, each as a reply record with parentUrl. Full reply threads are not paginated.
Can I download Threads videos or images?
No. Records include media URLs, which can expire, but files are not downloaded.
Related Actors
- Linktree Scraper — Link-in-Bio Links, Socials & Emails: creator link pages, socials and published contacts.
- Instagram Trending Reels Scraper: a ranked sample of trending Instagram Reels.
- Truth Social Scraper: public Truth Social posts and profiles.
- LinkedIn Post Scraper — Company Page Posts: posts from public LinkedIn company pages.
- Reddit Buyer Intent & Brand Monitor: brand mentions and buyer-intent posts on Reddit.
Legal and compliance
The Actor collects public Threads content only. Usernames, posts and profile details can be personal data, so process them under a lawful basis, keep only what you need and follow Threads' terms. This is an independent tool and is not affiliated with Meta or Threads.
Last verified: 2026-10-27