Threads Scraper

Threads Scraper: public profiles and recent posts, no login

Give it Threads handles and get back a row for each profile plus their recent public posts. Bio, follower count, post text, likes, the exact publish time, image links, and flags for video and replies. Nothing to log into.

You have to know whose posts you want. There is no anonymous global search on Threads that holds up, so this reads the handles you list and nothing wider. The query field filters those posts, it does not search Threads.

🔍 What Threads Scraper does

Threads lives on threads.com now. A threads.net link redirects across, so both forms work, and so does a bare handle like zuck. Duplicates in your list are collapsed before anything is fetched, whatever the capitalisation.

For each handle it reads the public profile, then the public feed of that account's recent posts. You get one profile row and up to 30 post rows per handle, and you can turn the profile rows off if all you want is the posts.

query is an optional case-insensitive text filter over the posts it collected, so you can run ten accounts and keep only the ones that said "pricing". It narrows what you already asked for. It does not reach any post from an account you did not list.

📥 What you give it

{
  "profiles": ["zuck", "https://www.threads.com/@instagram"],
  "maxPostsPerProfile": 10,
  "includeProfile": true,
  "query": "AI"
}

Leave profiles empty and you get a single labelled sample row, so you can see the shape before committing a list.

📤 What you get back

Every row carries a recordType, so one pass over the dataset splits it. A real profile row and a real post row, with the avatar URL cut short:

{
  "ok": true,
  "recordType": "profile",
  "id": "63055343223",
  "username": "zuck",
  "displayName": "Mark Zuckerberg",
  "bio": "Mostly superintelligence and MMA takes. See the latest conversations with @zuck.",
  "followerCount": 5700000,
  "isVerified": null,
  "profilePicUrl": "https://scontent-iad3-1.cdninstagram.com/v/t51.82787-19/550174606_...",
  "profileUrl": "https://www.threads.com/@zuck",
  "source": "threads_public_ssr"
}
{
  "ok": true,
  "recordType": "post",
  "id": "3981852126213720917",
  "postId": "3981852126213720917",
  "username": "zuck",
  "text": "Introducing @Muse, the personal agent that understands your goals and works 24/7 to get things done for you...",
  "likeCount": 3007,
  "publishedAt": "2026-09-08T18:56:24.000Z",
  "postCode": "DdCYWl7GktV",
  "postUrl": "https://www.threads.com/@zuck/post/DdCYWl7GktV",
  "imageUrls": [],
  "hasVideo": false,
  "isReply": false,
  "source": "threads_public_graphql"
}

🧾 Reading the output

The sample row also carries recordType: "profile", so filter on _sample and _diagnostic being absent rather than on recordType alone.

A diagnostic row names the handle it belongs to and carries a code:

▶️ How to run it

1. Open Threads Scraper and click Try for free. 2. Put your handles into Threads profiles, one per line. 3. Set Maximum recent posts per profile. Ten is plenty for a first look. 4. Click Start. 5. Download the dataset as JSON, CSV or Excel, or read it from the Apify API.

💰 How much does it cost?

$0.40 per 1,000 rows. Flat on every Apify plan, no volume tiers.

A profile row and a post row cost the same. Turning Include profile rows off is the cheapest way to run a posts-only monitor, because a skipped profile row is a row you are not billed for. The sample row is not charged, diagnostic rows are not charged, and a handle you listed twice only produces one set of rows.

💡 What people use it for

• Watching what a set of accounts posted this week, on a schedule, with postCode as the dedupe key.
• Pulling the text of an account's recent posts into a summary or a newsletter without opening the

app.

• Tracking like counts on a competitor's posts over time, by running the same handles daily and

joining on postId.

• Filtering a list of industry accounts down to the posts that mention one word, using query, so a

30-account sweep lands as a handful of rows.

• Collecting bios and follower counts for a list of creators before deciding who to approach.

🚧 What it does not do

• No global search. You cannot ask for every post mentioning a word. You give it handles.
• No hashtags, no follower lists, no following lists, no reply threads and no comments under a

post.

• A bad handle can end the run. One entry that is not a usable handle stops the batch before the

good handles are written, and you get a single TARGET_ERROR row instead of your data. Check the list before a long run.

• isVerified is always null.
• followerCount is rounded whenever Threads abbreviates it.
• 30 posts per profile is the hard ceiling, and recent posts only. There is no way back through

an account's history.

• Public accounts only. A profile that does not resolve publicly comes back as a diagnostic row.
• Image links are Meta CDN URLs. They work for a while and are not archival. Video is a flag, not

a file.

• Rows are a snapshot. Likes move and posts get deleted.

🧭 Which social scraper do you need?

❓ Questions people ask

Do I need a Threads or Instagram login? No. Nothing to connect, no cookie, no token.

Can I search Threads for a keyword? Not from here. query filters the posts from the accounts you listed. A real global search is not something Threads exposes to a signed-out visitor.

Do threads.net links work? Yes. They redirect to threads.com and resolve to the same account.

Why is the follower count round? Because Threads publishes it round for big accounts. A 5.7M on the page becomes 5700000 here.

Can I monitor accounts daily? Yes. Schedule it, keep includeProfile off if you only want posts, and dedupe on postCode.

Is this legal? These are public profiles and public posts. They are also personal data, which GDPR and similar laws cover, so have a reason for collecting it. Apify's write-up on scraping and the law is a good starting point, and we are not lawyers.

🆘 If something breaks

Open the Issues tab on the actor page. Send the handle and the run ID. If you got a diagnostic row, its code and details usually name the problem on their own.