Threads Scraper & Profile Monitor — New Posts Only, No Login

Scrape public Threads (threads.net / threads.com) profiles and get back only what changed: posts that appeared since your last run, their likes, replies, reposts and quotes, and how the follower count moved.

No login. No cookies. No browser automation — just fast HTTP requests, which is why runs finish in seconds.

Built for brand monitoring, competitor tracking and creator research — anywhere you need to know when something new happens rather than re-downloading the same posts every day.

Nothing new, nothing to pay

Most scrapers hand you the same posts on every run and bill you for all of them. This one remembers what it already gave you.

• A profile is charged only when it returns at least one new post
• Posts you received in a previous run are never charged again
• Private profiles, unreachable profiles and runs that find nothing new cost nothing

Your first run has nothing to compare against, so it returns the current posts as a baseline. From the second run onward you get only the difference.

What you get per profile

Field	Contents
profile	Username, user id, follower count, verified and private flags, profile picture
followerDelta	Follower change since your previous run
newPosts	How many new posts this run found
posts[]	Each new post: text, URL, publish time, likes, replies, reposts, quotes, media
posts[].engagementDelta	How much each post's numbers moved since last time
firstRun	Whether this was the baseline run for that profile
charged	Whether this row was billed

Input

{
  "usernames": ["@zuck", "mosseri", "https://www.threads.net/@nasa"],
  "onlyNewPosts": true,
  "includeEngagementDelta": true,
  "skipReplies": false,
  "maxPostsPerProfile": 25
}

Handles, plain usernames and full profile URLs all work. Duplicates and malformed entries are dropped before any work starts, so you are never billed for them.

Output

{
  "username": "zuck",
  "profile": {
    "username": "zuck",
    "userId": "63055343223",
    "followers": 5709931,
    "isVerified": true,
    "isPrivate": false
  },
  "followerDelta": 6,
  "newPosts": 1,
  "posts": [
    {
      "code": "Db2wI-DilLt",
      "url": "https://www.threads.com/@zuck/post/Db2wI-DilLt",
      "text": "Today we're also opening the weights for...",
      "publishedAt": "2026-08-10T09:21:59.000Z",
      "likes": 1654,
      "replies": 208,
      "reposts": 81,
      "quotes": 43,
      "isNew": true,
      "engagementDelta": { "likes": 12, "replies": 3, "reposts": 0, "quotes": 1 }
    }
  ],
  "firstRun": false,
  "charged": true
}

Pricing

Event	Price	When
profile-checked	$0.005	A profile returned at least one new post
post-delivered	$0.002	Per new post delivered

Checking a profile that has nothing new triggers neither event.

Scheduling

This actor is designed to run on a schedule. Point it at your profiles, run it hourly or daily, and each run hands you just the new material. Combine it with Apify's integrations to push new posts straight to Slack, a webhook or a spreadsheet.

Data sources

Public Threads profile pages only. No login, no cookies, no browser automation — the actor reads the same page any visitor can open. Public profile pages expose a limited window of recent posts, which is what this actor returns.

Legality and ethics

Is it legal to scrape Threads? Scraping publicly available data is generally legal — see Apify's guide on the legality of web scraping. This actor only reads what users have chosen to publish openly. It never logs in, never sends cookies, never touches private accounts, and never bypasses any access control.

Where this actor goes beyond the usual baseline:

• It says who it is. Requests carry an honest, identifiable User-Agent instead of impersonating a browser — the transparency Apify recommends for ethical scraping.
• It asks for less. Posts already delivered are never re-requested, so repeat runs put a fraction of the load on Threads that a full re-scrape would.
• It skips what it doesn't need. Only public profile fields and public post metrics are collected.

Your responsibility. Results can still contain personal data such as usernames and public bios, which is protected under GDPR and comparable laws worldwide. Do not collect or process personal data without a legitimate basis for doing so, and make sure your intended use complies with the law in your jurisdiction and with Threads' own terms. If you are unsure whether your use case qualifies, consult your lawyer.

Disclaimer

This is an unofficial actor. It is an independent tool and is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc., Instagram, or Threads. All trademarks are the property of their respective owners.