Social Media · Threads Scraper

Threads User Posts Scraper API

Pull everything a Threads account has posted, page by page, with text, media, and reply, repost and like counts. No headless browsers, no captchas, proxies included.

$1.49per 1k callsJSONevery response1required parameter

Start scraping Threads API reference

// Threads · User Posts

curl -H "X-API-Key: hpx_your_key_here" \

"https://hproxy.com/api/v1/scrape/threads/posts?handle=zuck"

// → { "data": { … }, "records": 1, "costUsd": … }

Platform

Threads

What you scrape

Everything5 Profiles1Posts and media2Search and trends2

From Request to Clean JSON

You write one line. We do everything between the request and the data.

You send

One API call

GET the Threads endpoint with your key. That's all your code does.

We handle

Proxies · captchas · parsing

Residential exit, anti-bot walls, JS rendering and extraction, all server-side, on us.

You get

Clean JSON

A structured object every time. No HTML, no scraping code, no maintenance.

The Threads User Posts endpoint is one API call: send an account handle with your HProxy key and get back a clean, structured JSON object. Pull everything a Threads account has posted, page by page, with text, media, and reply, repost and like counts. HProxy runs the proxies, sessions, anti-bot handling and parsing server-side, so there is no headless browser to babysit and no parser to keep fixing when Threads changes its markup. You only ever touch the JSON.

What the Threads User Posts API returns

posts[]

Each post with text, media and permalink.

author

Poster handle, ID and display name.

stats

Reactions, comments and shares per post.

createdAt

Publish timestamp, so you can sort and dedupe.

Example response

200 OK · application/json

{
  "posts": [
    { "id": "88120...", "text": "we just shipped something big",
      "author": { "username": "@handle" },
      "media": [ { "type": "photo", "url": "https://.../img.jpg" } ],
      "stats": { "reactions": 4120, "comments": 214, "shares": 88 },
      "createdAt": "2026-07-28T11:04:00Z" }
  ],
  "cursor": "eyJwYWdlIjoyfQ"
}

Trimmed for brevity. Every call returns the full object with all fields listed here.

The Threads user posts endpoint

Full Threads reference

GET/api/v1/scrape/threads/posts

Parameters

handlestringrequired

Account handle or @username.

user_idstringoptional

Identifier from a previous response.

trimbooleanoptional

Return a slimmed-down payload (drops verbose fields).

Example request

cURL

curl "https://hproxy.com/api/v1/scrape/threads/posts?handle=zuck" \
  -H "X-API-Key: hpx_your_key_here"

POST with a JSON body works too. Errors, timeouts and rate limits are never billed; a target that does not exist counts as a call.

Scraping Threads user posts in three steps

Create a free account

Grab your API key

One key from the dashboard authenticates every scraper, Threads user posts included.

Call the endpoint

Send the target to the Threads User Posts endpoint and read the JSON. That is the whole integration.

No captchas, ever

Anti-bot walls, JS rendering and rate limits are handled server-side. You call an API, that is the whole job.

Residential-backed

Every request exits through HProxy's own residential network, so it looks like a real user on a real device.

Pay per call

No subscription, no seat licenses. Calls are billed from your balance and the balance never expires.

Fresh on every call

Responses are scraped live at request time, no stale cache dressed up as data.

Errors are free

Blocked, errored or timed-out calls are not charged. A target that does not exist counts as a call, because the platform still had to be asked.

Scales with you

From one call to millions: same endpoint, same price curve, volume discounts as you grow.

What people build with it

Track everything an account publishes, automatically.

Feed a content archive or compliance record.

Benchmark posting cadence and engagement against rivals.

Threads User Posts pricing

$1.49

per 1,000 calls · 0.15¢ each

Pay per call, no subscription

Errors and timeouts are not charged

Proxies included in the price

Get started free

Threads User Posts scraper FAQ

How do I scrape Threads user posts?

Send one authenticated HTTPS request to the Threads User Posts endpoint with an account handle and your HProxy API key. Pull everything a Threads account has posted, page by page, with text, media, and reply, repost and like counts. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.

What does the Threads user posts scraper return?

A structured JSON object with the full user posts data Threads exposes publicly. See the fields listed above. The schema is consistent across calls, so you integrate once and rely on it.

How much does it cost to scrape Threads user posts?

This endpoint is 0.15¢ per successful call, which is $1.49 per 1,000. It bills from your HProxy balance with no subscription and no monthly minimum. Errors are retried and never charged; a lookup whose target does not exist counts as a call.

Do I need my own proxies to scrape Threads?

No. Every call runs on HProxy's own residential network behind the scenes, so requests look like real users. The proxy layer is already included in the per-call price.

Is scraping Threads user posts allowed?

The API only accesses publicly available Threads data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and Threads's terms for your use case.

The same data on other platforms

All Post Scraper API endpoints

Facebook Profile Posts

Facebook Post

Facebook Group Posts

YouTube Community Post

More Threads scrapers

All Threads endpoints

Threads Post Threads Profile Threads Search Threads Search Users

HProxy.

Ready when you are.Your dashboard is ten seconds away.

Get Started Talk to us

Or talk to us at support@hproxy.com

HProxy