👁 🧵 Threads User Posts Scraper avatar

🧵 Threads User Posts Scraper

Pricing

from $3.99 / 1,000 results

Try for free

Go to Apify Store

👁 🧵 Threads User Posts Scraper

🧵 Threads User Posts Scraper

Try for free

Pricing

from $3.99 / 1,000 results

Rating

0.0

(0)

Developer

👁 ScraperX

ScraperX

Maintained by Community

Actor stats

Bookmarked

Total users

Monthly active users

4 days ago

Last modified

Threads User Posts Scraper

Apify actor that collects public posts from Threads profiles using the same GraphQL + HTML token strategy as the reference scripts (helper.py, main.py, extract_output.py).

Behavior

Requests start without a proxy (direct to threads.com).
If Threads blocks or rejects traffic, the actor switches to an Apify datacenter proxy and keeps using that tier for the rest of the run (until another escalation is needed).
If datacenter is unavailable or still blocked, it switches to an Apify residential proxy and performs up to three attempts per profile with rotated residential sessions.
Posts are pushed to the dataset as they are parsed (live saving).

Input

Field	Description
`urls`	Profile URLs (`https://www.threads.com/@user`) or usernames; bulk supported.
`maxPostsPerProfile`	Max posts per profile (1–500, default 100).
`proxyConfiguration`	Optional. Omit it or use No proxy in the console; backup routing still uses your Apify account proxies when needed.

Field taken_at uses the actor container’s local timezone (same as the original script’s default).

Output

Dataset items match the reference output.json shape: profile_pic_url, username, id, pk, code, caption, engagement fields, audio, medias, tags, mentions, taken_at, url, etc.

Local run

pip install-r requirements.txt
exportAPIFY_LOCAL_STORAGE_DIR=./storage
# Put INPUT.json in storage/key_value_stores/default/INPUT.json
python -m src

Legal

Data is taken from publicly visible Threads content only. You are responsible for compliance with applicable laws and Meta’s terms.