Threads Scraper

Extract posts, captions, engagement metrics, and media from Threads (by Meta) profiles and direct post URLs. No API key, no login, no browser.

What does Threads Scraper do?

Scrape public Threads content in four modes:

• Profile posts — pass usernames, get their recent posts with caption, likes, replies, reposts, quotes, media, and timestamps.
• Direct post URLs — pass Threads post URLs, get the specific post's full record.
• Keyword search — pass keywords, get ~20–25 matching public posts per query. Batch many queries to scale.
• Hashtag search — pass hashtags, get ~20–25 matching public posts per hashtag.

Uses the server-rendered HTML that Threads serves to crawler and browser user agents, with residential proxy rotation to avoid per-IP throttling. No login, no API key, no browser. No GraphQL signing, no PoToken, no Cloudflare managed challenge.

Output fields

Field	Description
code	Threads post short code
url	Direct post URL
authorUsername	Author handle
authorFullName	Author display name
authorId	Author ID
authorVerified	Verified flag
caption	Post text (truncated to 5,000 chars)
likeCount	Likes
replyCount	Direct replies
repostCount	Reposts
quoteCount	Quotes
shareCount	Shares
takenAt	ISO 8601 timestamp
mediaUrls	Image and video URLs
mediaType	image / video / text
language	Post language
isReply	Reply flag
query	The keyword or hashtag that surfaced this post (search modes only)
sourceType	keyword or hashtag (search modes only)

Who is it for?

• Social media managers tracking competitor posting cadence and engagement
• Content researchers analyzing top-performing posts by topic or account
• Brand monitoring teams watching product mentions
• Growth teams building cross-platform creator databases
• Data scientists building Threads engagement datasets

Pricing

$1.60 per 1,000 results. No subscription.

Results	Cost
100	$0.16
1,000	$1.60
10,000	$16.00

How to use it

1. Pick a Mode.
2. For profile mode: enter Usernames.
3. For search mode: enter Search Queries. For hashtag mode: enter Hashtags. Batch 10–50 queries to scale.
4. Set Max Items (default 100) and Max Posts per Query (default 50).
5. Click Start.

Output example

{
  "recordType": "threads-post",
  "postId": "3412345678901234567",
  "code": "C1a2B3c4D5e",
  "url": "https://www.threads.net/@zuck/post/C1a2B3c4D5e",
  "authorUsername": "zuck",
  "authorFullName": "Mark Zuckerberg",
  "authorId": "123456789",
  "authorVerified": true,
  "caption": "Great conversation on the future of AI...",
  "likeCount": 45200,
  "replyCount": 1200,
  "repostCount": 890,
  "quoteCount": 45,
  "shareCount": null,
  "takenAt": "2026-09-20T14:30:00.000Z",
  "mediaUrls": ["https://scontent.cdninstagram.com/..."],
  "mediaType": "image",
  "language": "en",
  "isReply": false,
  "context": "@zuck",
  "scrapedAt": "2026-09-22T12:00:00.000Z"
}

Technical details

• No API key, no login, no browser. Uses Threads' public GraphQL endpoint (graphql.threads.net) — the same endpoint Meta serves to unauthenticated visitors.
• Crawler-UA SSR path — Threads serves full server-rendered HTML to facebookexternalhit and browser user agents. The actor parses JSON-LD, data-sjs blocks, and raw post codes from that HTML.
• Residential proxy built-in. Threads throttles datacenter IPs after a few requests. All fetches route through Apify's residential proxy automatically.
• Session cookie harvesting — the actor captures sessionid/csrftoken from the initial HTML response if present, for requests that benefit from a session.

Known limits

• Profile mode is capped at ~25–30 posts per profile by Threads itself. Logged-out profile views return only the most recent posts. This is not an actor limitation — every Threads scraper on the market hits this same ceiling.
• Search mode returns ~20–25 posts per query. Threads does not paginate logged-out search results. To scale, batch 10–50 queries (or hashtags) in a single run.
• Public content only. Private profiles and protected posts are not accessible.
• Caption truncated at 5,000 characters.
• Comment/reply scraping not supported in this version.
• Residential proxy is required. Threads throttles datacenter IPs after a handful of requests. The actor routes all fetches through residential proxy automatically.

FAQ

Do I need a Threads account? No. The actor scrapes public content without authentication.

Do I need a proxy? No. Datacenter IPs work for public Threads content.

Why is search limited to ~20 posts per query? Threads does not paginate logged-out search results. Each query returns a single batch. To scale, pass 10–50 queries in one run — the actor dedupes across all of them.

How many posts can I get per profile? Up to 50 by default (maxPostsPerProfile), configurable to 500.

How do I export data? After a run, go to Storage → Export as JSON, CSV, Excel.

Support

Open an issue on the Actor's page for bugs or feature requests.