Threads Post Engagement Scraper

Extract public Threads post engagement metrics from threads.com and threads.net URLs. This Actor returns post text, author details, timestamps, media, likes, replies, reposts, quotes, and a calculated engagement count in a clean Apify dataset.

It uses a fast HTTP/Cheerio pass first and automatically retries incomplete pages in a controlled browser. You do not need a Threads login, cookies, or an API key. Run it manually, schedule it, call it through the Apify API, or connect the dataset to Google Sheets, Make, Zapier, and other integrations.

Disclaimer: This unofficial Actor is not affiliated with or endorsed by Meta Platforms, Inc. Scrape only public information and follow Threads’ Terms of Service and applicable laws.

What does Threads Post Engagement Scraper do?

Give the Actor one or more public Threads post URLs. It validates and deduplicates them, reads the public page, and returns normalized post records. Both threads.com and the legacy threads.net host are supported.

The Actor uses Apify features including API access, scheduling, proxy rotation, monitoring, automatic retries, and dataset exports. If Threads serves a JavaScript-rendered page or temporarily blocks the HTTP response, the Actor uses a browser fallback for that post.

Why use Threads Post Engagement Scraper?

• Track the performance of posts over time with scheduled runs.
• Compare likes, replies, reposts, quotes, and total engagement across creators or campaigns.
• Build datasets for social listening, content research, reporting, and analytics.
• Keep the output consistent even when individual engagement fields are unavailable.
• Process batches of up to 1,000 post URLs with automatic duplicate removal.

How to scrape Threads post engagement

1. Open this Actor in Apify Console or run it locally.
2. Add public Threads post URLs in the Input tab.
3. Optionally configure concurrency or enable an Apify proxy.
4. Start the run and open the Output tab.
5. Download the dataset or consume it through the Apify API.

Input

The required startUrls field accepts public post URLs such as:

{
    "startUrls": [
        { "url": "https://www.threads.com/@creator/post/AbC_123" },
        { "url": "https://threads.net/t/Def_456" },
        { "url": "https://www.threads.com/share/GbKn-Nmue/" }
    ],
    "maxConcurrency": 10,
    "proxyConfiguration": { "useApifyProxy": false }
}

The Actor accepts /@username/post/CODE, /t/CODE, and /share/TOKEN redirect links on threads.com or threads.net. Share links are followed automatically and the resolved post URL is used when Threads redirects successfully. Query parameters are ignored for deduplication. maxConcurrency defaults to 10 and is capped at 25. A proxy is optional, but residential proxy traffic can help when Threads rate-limits requests.

Output

Each successful or partial record represents one normalized post:

{
    "postId": "post-123",
    "code": "AbC_123",
    "url": "https://www.threads.com/@creator/post/AbC_123",
    "text": "A post about public data #scraping",
    "sharedUrl": "https://example.com/resource",
    "sharedThumbnailUrl": "https://cdn.example/resource-thumbnail.jpg",
    "createdAt": "2026-01-02T03:04:05.000Z",
    "likeCount": 1200,
    "replyCount": 42,
    "repostCount": 8,
    "quoteCount": 3,
    "engagementCount": 1253,
    "author": { "username": "creator", "isVerified": true },
    "status": "success",
    "missingFields": []
}

Partial records retain all fields that were found and list unavailable engagement fields in missingFields. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

Data table

Field	Description
postId / code	Threads identifiers
url / originalUrl	Canonical and submitted URLs
text	Public post text
sharedUrl	First external URL shared by the post
sharedThumbnailUrl	Preview thumbnail URL, first caption URL, or first extracted image
author	Username, name, verification, profile, and avatar data
createdAt	Post creation timestamp
likeCount	Like or reaction count
replyCount	Reply or comment count
repostCount	Repost count
quoteCount	Quote count
engagementCount	Sum of all four counts when all are available
media	Public image and video URLs
hashtags / mentions	Tags and mentions parsed from text
status	success or partial

How much does it cost to scrape Threads posts?

Apify charges for the compute and storage used by your run. HTTP requests are inexpensive; browser fallback uses more compute and is limited to pages that need it. Your Apify account includes free monthly usage subject to the current Apify plan and pricing. The Actor does not require a third-party API subscription or user-provided key.

Tips and advanced options

• Start with a small batch to verify that the target posts are public.
• Lower maxConcurrency if you see rate limiting; enable Apify Proxy for larger runs.
• Use scheduled runs to create historical engagement snapshots rather than overwriting old datasets.
• Treat partial rows as usable leads for analysis, but check missingFields before calculating totals.

FAQ, disclaimers, and support

Does this require a Threads login?

No. The Actor reads public pages only and does not accept or store login credentials or cookies.

Does it scrape profiles, searches, or replies?

This version is focused on the post URLs you provide. Profile timelines, keyword search, pagination, and reply-thread expansion are outside the current scope.

Why is a record partial?

Threads may hide a metric, return a consent or login page, or render information only after JavaScript executes. The Actor preserves available data and reports missing engagement fields instead of inventing zero values.

Is scraping Threads legal?

You are responsible for complying with Threads’ Terms of Service, robots policies, privacy obligations, and applicable laws. Use the Actor only for public, lawful data collection.

For feedback or bug reports, use the Actor’s Issues tab. Custom extraction fields and private integrations can be developed as a separate solution.