Threads Post Scraper

Export public Threads posts and visible replies from specific post URLs into structured JSON, CSV or Excel. Threads Post Scraper returns text, authors, engagement, media, timestamps and conversation links for social listening, campaign reporting and public-source research without a Threads login. Only publicly available content is collected, and not every reply or metric is exposed.

Quick start

Paste one or more public Threads post URLs into Public Threads post URLs, choose a small row limit and click Start. When the run finishes, open its dataset to inspect the records. For API users, this bounded input collects up to ten combined post and reply rows:

{
  "postUrls": [{"url": "https://www.threads.com/@openai/post/DW7RXR7EnRC"}],
  "maxItems": 10,
  "includeReplies": true,
  "maxRepliesPerPost": 9,
  "includeAuthorProfile": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to inspect and reuse its existing input:

• Export a Public Threads Post — Save one root post without replies.
• Analyze a Threads Post and Visible Replies — Save a root post and up to nine visible replies within a ten-row limit.
• Monitor Multiple Public Threads Posts — Collect root posts from two URLs without replies. Comparing successive collections is a separate workflow step.

What you get

• Root posts and available public replies as separate rows.
• Post text, author identity, timestamps and canonical source URLs.
• Available likes, reply counts, reposts, quotes, shares and public view counts.
• Image, video and carousel links with accessibility captions when exposed.
• Hashtags, mentions, external links and conversation relationships.
• Optional public root-author biography and follower count when available.

Who is it for?

• Social listening teams: review specific posts and their visible conversation context.
• Brand marketers: export campaign-post engagement and media evidence.
• PR teams: retain source URLs, timestamps and public metrics for reporting.
• Public-source researchers: organize records using root and parent identifiers.

Input settings

Setting / API key	Type	Default	Description
Post URLs (postUrls)	array	required	Public threads.com/@username/post/code URLs or Threads share links.
Row limit (maxItems)	integer	10	Maximum combined root-post and reply rows to save.
Visible replies (includeReplies)	boolean	true	Save visible public replies as linked rows.
Reply limit (maxRepliesPerPost)	integer	20	Maximum visible replies saved for each root post.
Author enrichment (includeAuthorProfile)	boolean	false	Request bounded public author-profile enrichment when available.
Legacy option (failOnBlocked)	boolean	false	Accepted but ignored. Unavailable targets produce empty/partial results. Systemic failures still fail.

The row limit combines root posts and replies across the whole batch. Public Threads share links are also accepted. For a post-only input, set includeReplies to false and maxItems to 1.

failOnBlocked remains accepted for existing inputs but has no effect. No connection or proxy setting is supported.

Output data

Each dataset row represents a post or a visible reply. Unavailable optional values remain null rather than being estimated. This deliberately synthetic, abbreviated shape example is not an observed post:

{
  "itemType": "post",
  "postUrl": "https://www.threads.com/@example/post/EXAMPLE",
  "postId": "example-id",
  "text": "Example public post text",
  "username": "example",
  "likeCount": null,
  "viewCount": null,
  "isReply": false,
  "rootPostId": "example-id",
  "collectionStatus": "complete",
  "warning": null
}

Group	Fields
Identity	itemType, postUrl, postId, shortcode, sourceUrl, scrapedAt
Content	text, timestamp, language, hashtags, mentions, mentionedUsers, externalUrls, linkPreviewTitle
Author	username, userId, displayName, profileUrl, avatarUrl, isVerified, bio, followerCount
Engagement	likeCount, replyCount, repostCount, quoteCount, shareCount, viewCount, viewCountStatus
Media	mediaType, mediaUrls, mediaWidth, mediaHeight, accessibilityCaption
Conversation	isReply, isRepost, isQuotePost, replyToUsername, replyToPostId, replyControl, parentPostId, rootPostId
Reliability	collectionStatus, warning

The key-value store's RUN_SUMMARY contains per-input outcomes and reasons, warnings and saved-row totals. Those summary entries are not dataset records. If the time reserve is reached, PENDING_WORK identifies unfinished URLs.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

This Actor uses pay-per-event pricing. The start event is charged once, after the first row is saved. A run with no saved records does not incur this event.

The result event is charged for each saved root-post or reply row. Skipped targets and summary entries are not charged result rows. maxItems limits saved rows, not the number of input URLs.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start with a small batch. Inspect a few records before increasing your row limit.
• Use canonical post URLs. Old author links also work when Threads explicitly identifies the renamed author in the canonical URL for the same post.
• Choose replies deliberately. Reply rows share the total maxItems budget with root posts.
• Check the summary. RUN_SUMMARY.outcomes explains skipped, empty or unfinished inputs.
• Enable author enrichment only when useful. Public biographies and follower counts may still be unavailable.

Limits and caveats

The Actor processes specific public post URLs. It does not search Threads, enumerate whole profiles or guarantee every reply. It does not accept login cookies or retrieve private accounts, direct messages or private profile data.

Unavailable targets and completed extraction with no usable records can succeed with an empty dataset. An explicit Threads audience-restriction page produces the unavailable_audience summary reason without claiming the post is private or deleted. Inaccessibility alone does not establish privacy or deletion. Mixed batches retain useful rows and report target-specific outcomes.

Malformed entries are skipped when valid targets remain. At least one valid post URL is required. Systemic rate limits, upstream server errors and execution failures still fail the run. Saved records may remain available after a later failure.

Views, shares, author enrichment and other optional fields may be absent. Root-author enrichment is best effort and does not enrich every reply author. There is no built-in change detection or alerting.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~threads-post-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"postUrls":[{"url":"https://www.threads.com/@openai/post/DW7RXR7EnRC"}],"maxItems":10}'
# After completion, read the returned defaultDatasetId:
# curl -H "Authorization: Bearer $APIFY_TOKEN" \
#   "https://api.apify.com/v2/datasets/DATASET_ID/items?format=json"

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/threads-post-scraper').call({
  postUrls: [{ url: 'https://www.threads.com/@openai/post/DW7RXR7EnRC' }],
  maxItems: 10,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient
client = ApifyClient(token=os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/threads-post-scraper').call(run_input={
    'postUrls': [{'url': 'https://www.threads.com/@openai/post/DW7RXR7EnRC'}],
    'maxItems': 10,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

MCP and AI agents

You can ask your AI assistant to collect data with Threads Post Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Threads Post Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/threads-post-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Threads Post Scraper by Fetch Cat, or give it the identifier fetch_cat/threads-post-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Collect this public Threads post and its visible replies, up to ten records, then summarize the discussion.”
• “Export the root posts from these two public Threads links and compare their available engagement counts.”
• “Get this public Threads post with available author biography and follower count, then prepare a short research note with the source link.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export Threads posts without a login?

Yes. Supply public post URLs without cookies or a Threads account. Private and unavailable content is not retrieved.

Can I use this as a Threads post API?

Yes. Use the Apify API or supported MCP connection with specific public post URLs. This is not an official Threads API and does not support publishing posts.

Can I export CSV or Excel?

Yes. Export the run's dataset in Console. Use JSON when you need to retain nested media and mention fields.

Does it collect every reply?

No. Only replies exposed by the public post representation can be returned. The total row limit and per-post reply limit also apply.

Why did a run succeed without records?

A target can be unavailable or expose no usable post record. Check RUN_SUMMARY for truthful reasons. This does not establish privacy or deletion. Systemic execution failures still fail.

What does failOnBlocked do?

Nothing. It is an accepted legacy field and does not change outcomes.

Can I compare posts over time?

You can collect successive datasets through your own automation. Comparison and alerting must be implemented separately.

What is charged?

One start event after the first saved row and one result event per saved post or reply. See the live Pricing tab for current rates.

Related Actors

More Threads scrapers

• Threads Replies Scraper
• Threads Profile & Posts Scraper

• Website Contact Finder
• Bing Search Results Scraper
• Google Maps Lead Finder
• 2GIS Places Scraper

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥