Meta Threads Public Scraper

What does Meta Threads Public Scraper do?

Meta Threads Public Scraper collects public data from Threads without login. Point it at profile URLs, post URLs, or keyword search pages and export stable post IDs, usernames, text, engagement counts, and media URLs — with explicit extraction completeness flags so empty shells are not treated as successful rows.

Compatible with common inputs/outputs from popular Threads Store Actors (e.g. mode, keywords, max_posts, snake_case field aliases) so you can switch with minimal pipeline changes — while keeping public-only scraping, stable IDs, absolute media URLs, and hollow-row skipping.

Why scrape Threads?

• Brand monitoring — Track public mentions and keyword conversations.
• Creator research — Pull public profile bios, follower counts, and recent posts.
• Content analysis — Export post text, media URLs, and engagement for research workflows.
• Competitive listening — Compare public posting patterns across accounts and topics.

What data can you extract?

Field	Description
id / code / url	Stable Threads post pk, shortcode, and public post URL
userId / username / fullName	Public author identifiers
text	Post caption text
likeCount / replyCount / repostCount / quoteCount / shareCount	Public engagement metrics when present
imageUrl / imageUrls / videoUrls / mediaUrls / mediaUrl	Media CDN URLs (primary image + gallery)
followerCount / biography / isVerified	Profile fields on profile records and attached to posts when available
extractionComplete / extractionGaps	Honest completeness metadata (no silent hollow rows)
recordType	profile or post
Competitor aliases	Same values under snake_case keys (post_code, text_content, like_count, created_at, user_id, media_urls, …)

How to scrape public Threads data

1. Open the Actor in Apify Console.
2. Add start URLs such as https://www.threads.com/@zuck, a post URL, or https://www.threads.com/search?q=apify.
3. Optionally add usernames or search queries (or competitor-style mode + keywords + max_posts).
4. Set Maximum items per input (default 5).
5. Run the Actor and download JSON/CSV/Excel from the dataset.

Input

• Start URLs — profile, post (/@user/post/CODE or /t/CODE), or search URLs on threads.com / threads.net.
• URLs (alias) — optional alias for Start URLs.
• Usernames — bare names, @handle, or full profile URLs.
• Search queries — public keyword/hashtag terms.
• Keywords (alias) — competitor-compatible; search terms or optional keyword_match tags in user mode.
• Mode (optional) — user / search / profiles for competitor-style workflows.
• Maximum items per input — per URL / username / query (profile and post rows both count). Aliases: max_posts, resultsLimit.
• Search sort order — top or recent (search_filter).
• Start/end date — optional search date window (YYYY-MM-DD or 7 days).
• Include thread reply posts — keep author self-reply chain items when enabled. Alias: includeReplies.
• Include profile records — push one profile row before posts for profile inputs.
• Proxy configuration — optional; defaults to no Apify Proxy.

Competitor-compatible examples

User posts:

{
  "mode": "user",
  "usernames": ["zuck"],
  "max_posts": 5
}

Search:

{
  "mode": "search",
  "keywords": ["AI"],
  "search_filter": "recent",
  "max_posts": 5
}

Output example

{
  "recordType": "post",
  "id": "3957216315664483403",
  "code": "Dbq20Xaj8RL",
  "url": "https://www.threads.com/@zuck/post/Dbq20Xaj8RL",
  "text": "Announcing Muse Code beta...",
  "username": "zuck",
  "userId": "63055343223",
  "likeCount": 2445,
  "replyCount": 252,
  "imageUrl": "https://scontent.../...",
  "imageUrls": ["https://scontent.../..."],
  "mediaUrls": ["https://scontent.../..."],
  "extractionComplete": true,
  "extractionGaps": [],
  "sourceType": "profile",
  "sourceValue": "zuck",
  "record_type": "post",
  "post_code": "Dbq20Xaj8RL",
  "post_url": "https://www.threads.com/@zuck/post/Dbq20Xaj8RL",
  "text_content": "Announcing Muse Code beta...",
  "user_id": "63055343223",
  "like_count": 2445,
  "reply_count": 252,
  "created_at_timestamp": 1785956967,
  "media_urls": ["https://scontent.../..."]
}

FAQ

Do I need a Threads login or cookies?

No. The Actor only uses public pages. Private accounts and login-only feeds are out of scope.

Why are results limited to the first page?

Public crawlable HTML includes the first Relay batch of posts/search results. Logged-in pagination APIs are not used.

What about hollow or incomplete rows?

Rows without a stable id or without usable public fields are skipped. Partial rows keep extractionComplete: false and list gaps in extractionGaps.

Which URLs are supported?

https://www.threads.com/@username, https://www.threads.com/@username/post/CODE, https://www.threads.com/t/CODE, and https://www.threads.com/search?q=... (.net hosts are normalized).

Image Credit

Image credit: Threads