Skip to content
//Threads Scraper example\\

Threads posts from @zuck

A ready-to-run Threads Scraper input: Threads posts from @zuck.

Updated October 27, 2026

What this example returns

The dataset’s “Posts” view shows 11 columns: record_type, username, display_name, text_content, created_at, like_count, reply_count, repost_count, view_count, post_url, and source_tab. See every output field.

What each setting does

The input this example runs Threads Scraper with. “Try this input” opens it in the console, where you can run it as-is or change any field first.

Usernames usernames

zuck

Threads usernames or profile URLs, such as zuck, @zuck, or https://www.threads.com/@zuck. Used by user posts, reposts, and replies, and by find profiles when no keyword is given. Search ignores them.

.json
{
  "usernames": [
    "zuck"
  ]
}

What it costs

You pay for the events the actor reports, such as each result or page it produces, plus the platform usage of your runs: compute, proxies and storage. Platform usage is typically about $0.567 per 1,000 results.

  • Result$0.007One saved post or profile.

Full pricing

When to use this example

From the Threads Scraper readme:

Why are some view counts missing?

Threads does not show views on every post. Those rows have view_count empty and view_count_status set to not_public_yet.

Other ways to run Threads Scraper

All examples of Threads Scraper

About Threads Scraper

Collect public Threads posts, replies, reposts, and profiles. Search by keyword or read an account, with engagement, media, and profile fields. No login.

Price:
from $5.60 / 1,000 results
Developer:
Echofield
Category:
Social media

Threads Scraper pageOutput fieldsPricing

Related actors

//From the blog\\

Latest articles

All articles

The internet is full of data.
Start owning yours.

Scrape.ly gives you the infrastructure, the tooling, and the team to extract, process, and operationalize web data at any scale. Setup takes minutes.

No credit card. No setup calls.