Threads Replies Scraper API avatar

Threads Replies Scraper API

Pricing

from $1.00 / 1,000 results

Go to Apify Store
Threads Replies Scraper API

Threads Replies Scraper API

Fetch replies from Threads posts. Get reply text, engagement metrics, author info, and media details. Requires a Threads Session ID.

Pricing

from $1.00 / 1,000 results

Rating

5.0

(1)

Developer

Futurize Rush

Futurize Rush

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

2 days ago

Last modified

Share

Fetch replies from Threads posts and extract structured data including reply text, engagement metrics, author information, and media details.

What does Threads Replies Scraper API do?

This Actor fetches replies from Threads posts and returns structured data for each reply. You can process multiple post URLs in a single run.

Data you can extract

For the original post:

  • Post content — full text, post URL, shortcode, hashtags, mentions, URLs (including linked URLs from attached link cards)
  • Author info — username, user ID, profile URL, profile picture, verification status
  • Engagement metrics — likes, replies, reposts, quotes
  • Media details — media type, primary media URL, and all media URLs (carousel posts include one URL per slide)
  • Metadata — timestamp

For each reply:

  • Reply content — full text, reply URL, shortcode, hashtags, mentions, URLs (including linked URLs from attached link cards)
  • Author info — username, user ID, profile URL, profile picture, verification status
  • Engagement metrics — likes, reply count, reposts, quotes
  • Reply context — whether the post author liked it, who the reply is directed at
  • Media details — media type, primary media URL, and all media URLs (carousel posts include one URL per slide)
  • Metadata — timestamp, position index

How to get your Session ID

This Actor requires a Threads Session ID for authentication. Here's how to get it:

Option 1: Browser Developer Tools

  1. Open threads.com in your browser and log in
  2. Press F12 to open Developer Tools
  3. Go to ApplicationCookieshttps://www.threads.com
  4. Find the cookie named sessionid and copy its value
  5. Paste it into the Session ID field in the Actor input

You can also use a browser extension like Cookie-Editor to quickly view and copy cookies. Simply install the extension, visit threads.com, and search for the sessionid cookie.

Disclaimer: Cookie-Editor is a third-party extension not affiliated with this Actor. As with any browser extension that accesses cookie data, please review its permissions and use at your own discretion.

Important notes

  • Use a secondary account. Automated access may cause Threads to flag your account or temporarily restrict it. We strongly recommend using a secondary account rather than your primary one.
  • Session IDs have no guaranteed lifetime. They expire on logout, password change, new device login, or when Threads invalidates them for security reasons — which can happen unpredictably regardless of usage. If you receive authentication errors, obtain a fresh Session ID before retrying.
  • Rate limiting. Making too many requests in a short period may trigger rate limits. The Actor includes built-in delays, but very large runs may still be affected.

Input example

{
"postUrls": [
"https://www.threads.com/@zuck/post/DTa3-B1EbTp"
],
"sessionId": "your-session-id-here",
"maxReplies": 0,
"sortOrder": "top"
}
FieldTypeDescription
postUrlsArrayThreads post URLs to fetch replies from (1–50)
sessionIdStringYour Threads sessionid cookie
maxRepliesNumberMax replies per post (0 = unlimited, default: 0)
sortOrderStringReply sort order: "top" (most popular, default) or "recent" (newest first)

Output example

Original post (item_type: "post"):

{
"item_type": "post",
"sourceUrl": "https://www.threads.com/@zuck/post/DTa3-B1EbTp",
"postId": "3808602590024938729",
"replyId": null,
"postCode": "DTa3-B1EbTp",
"postUrl": "https://www.threads.com/@zuck/post/DTa3-B1EbTp",
"replyUrl": null,
"text": "Today we're establishing a new top-level initiative called Meta Compute...",
"hashtags": [],
"mentions": [],
"urls": [],
"username": "zuck",
"userId": "63055343223",
"profileUrl": "https://www.threads.com/@zuck",
"profilePicUrl": "https://scontent.cdninstagram.com/...",
"isVerified": true,
"timestamp": "2026-01-12T18:00:30.000Z",
"likeCount": 2714,
"replyCount": 866,
"repostCount": 129,
"quoteCount": 38,
"isLikedByAuthor": false,
"replyToUsername": null,
"mediaType": "text",
"mediaUrl": null,
"mediaUrls": [],
"index": null,
"scrapedAt": "2026-02-26T10:15:00.000Z"
}

Reply (item_type: "reply"):

{
"item_type": "reply",
"sourceUrl": "https://www.threads.com/@zuck/post/DTa3-B1EbTp",
"postId": null,
"replyId": "3808602587877435385",
"postCode": "DTa39_1EWf5",
"postUrl": null,
"replyUrl": "https://www.threads.com/@zuck/post/DTa39_1EWf5",
"text": "We will be partnering with big utilities to...",
"hashtags": [],
"mentions": [],
"urls": [],
"username": "zuck",
"userId": "63055343223",
"profileUrl": "https://www.threads.com/@zuck",
"profilePicUrl": "https://scontent.cdninstagram.com/...",
"isVerified": true,
"timestamp": "2026-01-12T18:00:30.000Z",
"likeCount": 862,
"replyCount": 92,
"repostCount": 31,
"quoteCount": 4,
"isLikedByAuthor": false,
"replyToUsername": "zuck",
"mediaType": "text",
"mediaUrl": null,
"mediaUrls": [],
"index": 1,
"scrapedAt": "2026-02-26T10:15:00.000Z"
}

How it works

  1. Validates your Session ID with Threads
  2. Fetches each post page to retrieve the original post data and (for Top sort) initial replies
  3. Extracts structured data from the page
  4. Loads more replies in the selected sort order until your limit is reached
  5. Saves results progressively — you can see data as it's collected

Tips for best results

  • Refresh your Session ID if you see errors. Session IDs can expire at any time. If authentication fails, obtain a fresh one and retry.
  • Use this Actor for on-demand scraping. Because Session IDs expire unpredictably, this Actor works best for manual runs rather than fully automated schedules.
  • Actual results may be fewer than expected. Posts with very few replies will naturally return fewer results regardless of your limit setting.

Frequently Asked Questions

Why does this Actor need a Session ID?

Threads requires authentication to return reply data. Without a valid session, the Actor cannot retrieve replies.

Is it safe to enter my Session ID?

Your Session ID grants access to your Threads account. We strongly recommend using a secondary account for this reason. The Session ID is used only to make authenticated requests to Threads — it is never stored, logged, or shared beyond your run.

I'm seeing authentication errors — what should I do?

Your Session ID has most likely expired. Follow the steps in How to get your Session ID to obtain a fresh one, then start a new run.

What does item_type mean in the output?

Each post URL produces one row with "item_type": "post" (the original post) followed by rows with "item_type": "reply" (one per reply). This lets you easily distinguish the post from its replies and filter by type.

What is the difference between "Top" and "Recent" sort?

"Top" returns the most popular replies based on engagement (default Threads view). "Recent" returns replies in chronological order, starting from the newest. Both sort modes may return different sets of replies — choose based on whether you want the most-engaged responses or the latest ones.

Can I scrape replies from multiple posts at once?

Yes. You can add up to 50 post URLs per run. Each post is scraped independently, and every result is labeled with the sourceUrl that produced it — making it easy to filter and compare by post.

Integrations

Connect Threads Replies Scraper API with other apps and services using Apify integrations. Export data to Google Sheets, Slack, Zapier, Make, and many more.

Disclaimer

This Actor is intended for learning, research, and personal use. Please use it responsibly and ethically, and ensure your usage complies with Threads' Terms of Service.

Threads may update its platform at any time, which could temporarily affect this Actor's functionality. While we actively maintain compatibility, occasional disruptions are possible.

Using a Session ID involves providing authentication credentials to the Actor. We strongly recommend using a secondary account, as automated access may result in account restrictions or temporary bans. You are solely responsible for how you use this tool and any consequences that may arise from its use.


Threads replies scraper, Threads comments scraper, Threads reply API, Threads reply extractor, Threads post replies, social media scraper, Threads analytics, Threads engagement analysis, Threads reply tracker, Apify actor, Claude Code, Gemini, Codex, OpenClaw