Social Media · Threads Scraper
Threads User Posts API
Pull a complete public Threads profile object (bio, counters, verification and links) as JSON. No headless browsers, no captchas, proxies included.
// Threads · User Posts
curl -H "X-API-Key: hp_live_••••••••" \
"https://hproxy.com/v1/scrapers/threads/user-posts"
// → { "data": { … }, "credits_used": 1 }
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 the target (a handle, URL, ID or query) with your HProxy key and get back a clean, structured JSON object. Pull a complete public Threads profile object (bio, counters, verification and links) as JSON. 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
bio / links
Public bio text and any linked URLs.
counts
Followers, following and post/video counts.
isVerified
Verification and account-type flags.
avatar
Profile image URL and display name.
Example response
{
"id": "1092...",
"username": "@handle",
"displayName": "Real Name",
"bio": "Founder. Building things.",
"isVerified": true,
"counts": { "followers": 90421, "following": 312, "posts": 1840 },
"links": ["https://example.com"],
"avatar": "https://.../avatar.jpg"
}Trimmed for brevity. Every call returns the full object with all fields listed here.
Scraping Threads user posts in three steps
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product and never expires.
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.
Failures are free
Automatic retries first; if an extraction still fails, the call is not charged.
Scales with you
From one call to millions: same endpoint, same price curve, volume discounts as you grow.
What people build with it
Enrich a CRM or lead list with live Threads profile data.
Verify accounts and detect fakes at scale.
Track competitor profiles and bios for changes.
Threads User Posts pricing
$3.00
per 1,000 calls · 0.3¢ each
Pay per call, no subscription
Failed extractions are not charged
Proxies included in the price
Threads User Posts scraper FAQ
How do I scrape Threads user posts?
Send one authenticated HTTPS request to the Threads User Posts endpoint with the target and your HProxy API key. Pull a complete public Threads profile object (bio, counters, verification and links) as JSON. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.
What does the Threads user posts API 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 the Threads user posts scraper cost?
It is pay per call from your HProxy balance, starting at $3.00 per 1,000 calls (0.3¢ per call). No subscription, no monthly minimum, and failed extractions are retried and not charged.
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.