Threads Scraper - Posts, Profiles, Replies and Search avatar

Threads Scraper - Posts, Profiles, Replies and Search

Pricing

from $1.60 / 1,000 results

Go to Apify Store
Threads Scraper - Posts, Profiles, Replies and Search

Threads Scraper - Posts, Profiles, Replies and Search

Threads scraper and unofficial Threads API. Scrape public Threads (Meta) posts, profiles, replies and keyword search results without login: text, likes, replies, reposts, quotes, media URLs and author details. Export to JSON, CSV or Excel.

Pricing

from $1.60 / 1,000 results

Rating

0.0

(0)

Developer

Nexus Cortex

Nexus Cortex

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

4 days ago

Last modified

Features

Limited permissions

Share

Threads Scraper & Unofficial Threads API: Posts, Profiles, Replies and Keyword Search (No Login)

Extract public data from Threads (threads.com / threads.net, by Meta) without an account, cookies or API key. Scrape the latest posts of any public profile, a single post with its replies, or search Threads by keyword, and export the results as JSON, CSV, Excel or via the Apify API.

Use it as an unofficial Threads API: call it from your code, Make, Zapier, n8n or Google Sheets and get Threads posts, profiles and replies as structured data, without creating a Meta developer app.

How to scrape Threads

  1. Click Try for free (or Start) on this page.
  2. Enter Threads usernames or profile URLs, post URLs, or search keywords.
  3. Set Maximum results to cap the size and cost of the run.
  4. Run the Actor, then download the Threads data as JSON, CSV or Excel, or read it through the Apify API.

What does Threads Scraper do?

  • Profile posts: give one or more usernames (or profile URLs) and get each account's latest posts, deep into the history (hundreds of posts per account), newest first.
  • Profile info: name, bio, follower count, verified badge and profile picture for each username.
  • Post and replies: give post URLs and get the post plus its replies, with likes, reply counts and author details.
  • Keyword search: search Threads for a keyword or phrase, sorted by relevance (top) or by time (recent).
  • Incremental runs: postsNewerThan (for example 24 hours) stops paging as soon as old posts show up, so scheduled monitoring runs stay cheap.

It works with plain HTTP requests against the same public endpoints Threads' own website uses for logged-out visitors. No browser is started, so runs are fast (roughly 300-800 results per minute in our tests) and cheap.

Why use it?

  • Brand and competitor monitoring: track what a company, creator or news outlet posts and how it performs.
  • Social listening and market research: pull the most recent posts that mention a product, topic or event.
  • Content and trend analysis: engagement (likes, replies, reposts, quotes), media type, links and topic tags per post.
  • Audience research: read the replies under a post.
  • Datasets for sentiment analysis, LLM pipelines and dashboards.

Input

FieldDescription
usernamesUsernames or profile URLs (zuck, @nasa, https://www.threads.com/@natgeo)
postUrlsLinks to single posts, including share links from the Threads app (threads.com/share/...)
searchQueriesKeywords or phrases to search
searchTypetop, recent or both
maxItemsHard cap on results for the whole run (also your cost cap)
resultsPerTargetMax posts per profile / keyword
maxRepliesPerPostMax replies per post URL (0 = only the post)
includeProfileInfoAdd one profile item per username
includeThreadContinuationsKeep the author's own follow-up posts in a thread
postsNewerThanDate (2026-10-01) or age (7 days, 12 hours)
proxyConfigurationApify Proxy settings (default on)

Example:

{
"usernames": ["zuck", "nasa", "https://www.threads.com/@natgeo"],
"postUrls": ["https://www.threads.com/@zuck/post/DfaNgswkQPG"],
"searchQueries": ["artemis"],
"searchType": "recent",
"maxItems": 200,
"resultsPerTarget": 50,
"maxRepliesPerPost": 20,
"postsNewerThan": "30 days"
}

Output

Each dataset item has a type: post, reply or profile. Download as JSON, CSV, Excel, XML or HTML.

Post example (shortened):

{
"type": "post",
"id": "4024588638696309702",
"code": "DfaNgswkQPG",
"url": "https://www.threads.com/@zuck/post/DfaNgswkQPG",
"username": "zuck",
"userId": "63055343223",
"userFullName": "Mark Zuckerberg",
"userVerified": true,
"text": "Using our new spaces feature on Muse to build a tool for my smoker. ...",
"createdAt": "2026-11-06T18:06:14.000Z",
"timestamp": 1793988374,
"likeCount": 1647,
"replyCount": 434,
"repostCount": 68,
"quoteCount": 23,
"mediaType": "carousel",
"images": ["https://scontent.cdninstagram.com/..."],
"videos": ["https://scontent.cdninstagram.com/..."],
"links": [],
"mentions": [],
"topicTag": "techthreads",
"linkPreview": null,
"quotedPostUrl": null,
"repostedPostUrl": null,
"isReply": false,
"replyToUsername": null,
"isPinned": false,
"language": "en"
}

Profile example:

{
"type": "profile",
"id": "63055343223",
"username": "zuck",
"url": "https://www.threads.com/@zuck",
"fullName": "Mark Zuckerberg",
"biography": "Mostly superintelligence and MMA takes",
"biographyLinks": [],
"followerCount": 5766526,
"isVerified": true,
"profilePicUrl": "https://scontent.cdninstagram.com/..."
}

Replies add parentPostCode and parentPostUrl; search results add searchQuery and searchSort. A run summary (items, items per minute, failed targets) is saved to the key-value store under SUMMARY.

Note: media and profile-picture URLs are signed Meta CDN links that expire after a few days. Download the files you need promptly.

How much does it cost?

You pay per result: one result event for every dataset item (post, reply or profile) written to the dataset. You pay nothing for failed targets or empty results. Set maxItems (and the run's maximum cost) to cap your spend; the Actor stops gracefully as soon as the limit is reached. See the pricing box on this page for the current price per 1,000 results. Each run also has Apify's standard start fee of $0.00005 ($0.05 per 1,000 runs), which covers the first seconds of compute. Apify subscribers pay less per result: 10% off on Bronze, 15% on Silver and 20% on Gold and higher plans.

Limitations (please read)

  • Public data only. Private accounts, and anything that needs a login, are not available and not attempted.
  • Keyword search returns one page: Threads does not paginate anonymous search, so each keyword returns about 10 to 20 posts per sort order. Use many keywords, recent sorting and scheduled runs for continuous monitoring.
  • Reposts are not included in profile feeds. Replies made by an account to other people's threads (the "Replies" tab) are not included either.
  • No view counts, follower lists or hashtag pages.
  • Meta changes its website regularly. If the Actor breaks, it fails with a clear error message instead of returning wrong data; please report it in the Issues tab.
  • Very large jobs benefit from the Residential proxy group if you see blocking errors in the log.

FAQ

Do I need a Threads or Instagram account? No. The Actor never logs in and never asks for cookies.

Does it scrape emails or phone numbers? No. It only returns what a public post or public profile shows, and does not extract contact data.

Is scraping Threads legal? The Actor collects only publicly visible data without logging in. In Meta v. Bright Data (N.D. Cal., January 2024) a US court held that Meta's terms do not bar logged-off scraping of public data. Laws differ by country and by what you do with the data (personal data is covered by GDPR and similar laws). This is not legal advice; make sure your use case complies with the laws that apply to you.

Is there an official Threads API? Why use this instead? Meta's official Threads API needs a Meta developer app, an access token and app review, and is built mainly for managing your own account. This Actor needs none of that: it reads the public posts, profiles, replies and search results any logged-out visitor can see.

Can I use it through the API or schedule it? Yes: use the Apify API, schedules, webhooks and integrations (Make, Zapier, Google Sheets, n8n, and more).

How many posts can I get per profile? Pagination works deep into an account's history (150 posts in 7 requests in our tests); set resultsPerTarget accordingly.

Something returned fewer results than I expected. Check the SUMMARY record in the key-value store; failed or non-public targets are listed there.

Feedback

Found a bug or need a field? Open an issue in the Issues tab and we will look at it. If this Actor saved you time, a short review on this page helps other users find it.

More scrapers from NexusCortex