Threads Profiles & Recent Posts Scraper

Collect public Threads profiles and their latest public posts without a Threads login. It uses an HTTP-only direct path: Threads' crawler-facing profile metadata resolves the public profile, then the public profile-posts query returns recent posts.

What it returns

Every row carries a recordType so you can split the dataset in one pass.

profile rows (recordType: "profile"):

Field	What it holds
username, displayName	the handle and the public display name
bio	public bio text
followerCount	approximate follower count, as Threads publishes it
profilePicUrl, profileUrl	avatar image and the canonical public profile URL
id, source	stable row id and the path the data came from

post rows (recordType: "post"):

Field	What it holds
postId, postCode, postUrl	ids and the canonical threads.com/@user/post/... link
username	the author handle
text	the public post text
likeCount	likes, or null when Threads does not expose a count
publishedAt	ISO timestamp
imageUrls	up to five public image URLs
hasVideo, isReply	booleans for media type and whether the post is a reply

diagnostic rows (recordType: "diagnostic") are deterministic free rows carrying a code — BLOCKED, RATE_LIMITED, NOT_FOUND, NETWORK or TARGET_ERROR — for invalid input, blocking, rate limits, target errors, no matching posts, or no results.

Only validated public profile and post rows are charged. Samples and diagnostics are never charged.

Input

{
  "profiles": ["zuck", "https://www.threads.com/@instagram"],
  "maxPostsPerProfile": 10,
  "includeProfile": true,
  "query": "AI",
  "fallbackToResidential": false
}

Field	Default	Notes
profiles	["zuck"] prefilled	public handles or full threads.com/@handle URLs; both forms are accepted
maxPostsPerProfile	10	1–30 genuine public posts saved per profile
includeProfile	true	set false to skip profile rows and pay only for posts
query	—	case-insensitive text filter applied to the posts from the profiles you supplied
fallbackToResidential	false	allow one bounded proxy retry after a block or transient failure
proxyConfiguration	proxy off	only used by that one fallback retry

query is intentionally account-scoped: Threads does not provide a reliable anonymous global search path, so this Actor does not claim one. Turning includeProfile off is the cheapest way to run a posts-only monitor, since each skipped profile row is one row you are not billed for.

Leave profiles empty to receive one clearly labelled, uncharged sample profile row.

Proxy behavior

The Actor always tries direct HTTP first. When fallbackToResidential is enabled and a direct request is blocked, rate-limited, or has a transient network failure, it makes one bounded retry using the supplied Apify proxy configuration. It does not retry successful requests and does not use a proxy for media downloads.

Pricing

$0.40 per 1,000 rows ($0.0004 each), plus $0.001 each time a run starts. Flat rate — no volume tiers, no plan gates — and you are charged only for rows actually returned.

A row is a genuine profile or post row. Samples, diagnostics, duplicates, blocked look-ups and no-result runs never incur the per-result fee — a run that returns nothing costs only the $0.001 start fee. Direct HTTP is the default path, so no residential bandwidth is billed unless you explicitly switch on fallbackToResidential.

Limits

• Public profiles and public posts only.
• maxPostsPerProfile is capped at 30 to keep costs and target load bounded.
• Profile follower counts are approximate when Threads abbreviates them in public metadata.
• Threads can change anonymous endpoints. A diagnostic row means no result was charged.

Use public data in accordance with applicable law and Threads' terms.