Threads (Meta) Scraper avatar

Threads (Meta) Scraper

Pricing

$1.00 / 1,000 records

Go to Apify Store
Threads (Meta) Scraper

Threads (Meta) Scraper

Scrape Meta Threads profiles and posts in guest mode: profiles with exact follower counts and bio, posts with caption, like/reply/repost counts, and replies. No login required.

Pricing

$1.00 / 1,000 records

Rating

0.0

(0)

Developer

Cravl

Cravl

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Threads (Meta) Scraper

Scrape Meta Threads profiles and posts in guest mode: no login.

What you get

  • Profiles: username, full name, bio, exact follower count, threads count, recent timeline posts
  • Posts: caption text, like/reply/repost counts, timestamp, author verification, and the reply tree

How it works

The engine re-fetches the raw server response (threads.net 30x-redirects to threads.com), walks the embedded Instagram-style post objects with a balanced-brace JSON scan, and merges the rendered-DOM state.

Input

FieldTypeDescription
directUrlsarrayProfile URLs (threads.net/@user) and/or post permalinks
proxyConfigurationobjectApify proxy settings

Output

Profile records: username, fullName, biography, followersExact, timeline[]. Post records: url, username, text, likes, replies, reposts, takenAt, repliesList[], repliesTotal.

Use cases

  • Threads profile monitoring with exact follower counts
  • Post engagement tracking (likes/replies/reposts)
  • Reply-thread extraction for conversation analysis

Migrating from other Apify Actors

Cravl Actors accept Apify-style inputs and emit familiar field names alongside Cravl-specific fields, so most pipelines migrate with minimal changes.

Input compatibility

  • startUrls (array of URLs, or objects with a url key) is accepted as an alias for directUrls.

Output compatibility

Post URLs emit one item with added aliases: likeCount, replyCount, retweetCount, postedAt, inputUrl. Profile URLs emit one profile item (record profile) followed by one item per timeline post (record post) with profileUrl and profileUsername context.