Threads Scraper — Posts, Profiles, Search & Hashtags avatar

Threads Scraper — Posts, Profiles, Search & Hashtags

Pricing

Pay per usage

Go to Apify Store
Threads Scraper — Posts, Profiles, Search & Hashtags

Threads Scraper — Posts, Profiles, Search & Hashtags

Scrape Meta Threads: posts, profiles, search, hashtags and replies. Hybrid engine (fast GraphQL + browser fallback). No login needed. Extract text, engagement metrics, media, hashtags and more.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Max Gor

Max Gor

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Scrape Meta Threads without login or API key. Extract posts, profiles, search results, hashtags, and full threads with replies.

Features

  • 5 modes in one actor: profiles, posts, threads, search, and hashtags
  • Hybrid engine: fast GraphQL API requests with automatic Playwright browser fallback
  • No login required — no tokens, no cookies
  • Rich data: text, engagement metrics (likes, replies, reposts), media URLs, hashtags, mentions
  • Proxy support with Apify Proxy (residential recommended)

Input

ParameterTypeDescription
modestringprofiles, posts, thread, search, or hashtags
profilesstring[]Usernames or profile URLs (for profiles and posts modes)
postUrlsstring[]Post URLs (for thread mode)
searchQueriesstring[]Search keywords (for search mode)
hashtagsstring[]Hashtag strings (for hashtags mode)
maxResultsnumberMax results per query/profile (default: 50)
proxyConfigurationobjectProxy settings

Example: Scrape user posts

{
"mode": "posts",
"profiles": ["zuck", "instagram"],
"maxResults": 20
}

Example: Search by keyword

{
"mode": "search",
"searchQueries": ["artificial intelligence", "web scraping"],
"maxResults": 50
}

Example: Get a thread with replies

{
"mode": "thread",
"postUrls": ["https://www.threads.net/t/C8H5FiCtESk"]
}

Example: Hashtag tracking

{
"mode": "hashtags",
"hashtags": ["tech", "ai"],
"maxResults": 100
}

Output

Posts

FieldTypeDescription
idstringThreads post ID
codestringShort code for URL
urlstringDirect link to the post
textstringPost content
usernamestringAuthor's username
userVerifiedbooleanVerified account badge
publishedAtstringISO 8601 timestamp
likeCountnumberNumber of likes
replyCountnumberNumber of replies
repostCountnumberNumber of reposts
imagesstring[]Image URLs
videosstring[]Video URLs
hashtagsstring[]Extracted hashtags
mentionsstring[]Extracted @mentions
isReplybooleanWhether this is a reply

Profiles

FieldTypeDescription
usernamestringThreads handle
fullNamestringDisplay name
biostringProfile bio
profilePicUrlstringAvatar URL
followerCountnumberFollowers count
followingCountnumberFollowing count
isVerifiedbooleanVerified badge
isPrivatebooleanPrivate account
externalUrlstringWebsite link

Use Cases

WhoWhat
Social media managersTrack brand mentions, monitor competitor content
MarketersAnalyze trending hashtags, measure engagement
ResearchersCollect public opinion data, study viral content
JournalistsMonitor public figures, track breaking stories
DevelopersFeed Threads data into apps, dashboards, analytics
InfluencersTrack engagement metrics, find trending topics

How it works

  1. GraphQL layer (fast, lightweight): Sends direct API requests to Threads' internal GraphQL endpoint — same requests the browser makes. No authentication needed. Works for profiles, posts, and threads.
  2. Playwright fallback (reliable): If GraphQL is blocked (403/429), automatically launches a headless browser. Also used for search and hashtag modes which don't have public GraphQL endpoints.
  3. Anti-bot resilience: User-Agent rotation, request delays, exponential backoff, and Apify Proxy integration.

Pricing

This actor uses a pay-per-result model:

ResultsCost
1,000~$1.00
10,000~$10.00
100,000~$100.00

Platform compute costs (memory + time) are additional. Recommended: 1 GB memory for most runs.

Tips

  • Use residential proxies for best reliability (Apify RESIDENTIAL group)
  • search and hashtags modes require a browser, so they use more memory and time
  • Keep maxResults reasonable (50-200) for faster runs
  • For monitoring, run the actor on a schedule (e.g., hourly hashtag tracking)

FAQ

Q: Do I need a Threads account? A: No. All data is scraped from public pages without login.

Q: What proxies should I use? A: Residential proxies work best. Set Apify Proxy with RESIDENTIAL group in the proxy configuration.

Q: Why are some posts missing text? A: Image-only or video-only posts may have no text content. The media URLs are still extracted.

Q: Can I monitor a hashtag over time? A: Yes! Schedule this actor to run hourly/daily with the same hashtag. Compare datasets to track trends.

Q: What's the difference between GraphQL and Playwright modes? A: GraphQL is faster and cheaper but may get blocked without proxies. Playwright is slower but more reliable. The actor switches automatically.

Integrations

  • Google Sheets — export directly from Apify
  • Webhooks — trigger on completion
  • API — fetch results programmatically
  • Zapier / Make — automate workflows
  • Slack / Email — get notified on new results

Limits

  • Threads may rate-limit or block requests — proxies help significantly
  • Private profiles return limited data
  • Search results depend on Threads' ranking algorithm
  • Media URLs are temporary (CDN links may expire)