Social Media · Threads Scraper

Threads Profile Scraper API

Pull a public Threads profile from a handle: bio, follower count, verification and the links on the profile. No headless browsers, no captchas, proxies included.

$3.00per 1k callsJSONevery response1required parameter

Start scraping Threads API reference

// Threads · Profile

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

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

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

Platform

Threads

What you scrape

Everything5Profiles1Posts and media2 Search 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 Profile endpoint is one API call: send an account handle with your HProxy key and get back a clean, structured JSON object. Pull a public Threads profile from a handle: bio, follower count, verification and the links on the profile. 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 Profile API returns

bio / links

Public bio text and any linked URLs.

counts

Followers, following and post or video counts.

isVerified

Verification and account-type flags.

avatar

Profile image URL and display name.

Example response

200 OK · application/json

{
  "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.

The Threads profile endpoint

Full Threads reference

GET/api/v1/scrape/threads/profile

Parameters

handlestringrequired

Account handle or @username.

trimbooleanoptional

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

cache_max_agestringoptional

Accept a cached result up to this old (1d, 3d, 7d, 14d or 30d) and pay nothing for it. Omit for a live scrape. Allowed values: `1d`, `3d`, `7d`, `14d`, `30d`.

Example request

cURL

curl "https://hproxy.com/api/v1/scrape/threads/profile?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 profile in three steps

Create a free account

Grab your API key

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

Call the endpoint

Send the target to the Threads Profile 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

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 Profile pricing

$3.00

per 1,000 calls · 0.3¢ each

Pay per call, no subscription

Errors and timeouts are not charged

Proxies included in the price

Get started free

Threads Profile scraper FAQ

How do I scrape Threads profile?

Send one authenticated HTTPS request to the Threads Profile endpoint with an account handle and your HProxy API key. Pull a public Threads profile from a handle: bio, follower count, verification and the links on the profile. No proxies, no headless browser and no parsing on your side. The response is ready-to-use JSON.

What does the Threads profile scraper return?

A structured JSON object with the full profile 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 profile?

This endpoint is 0.3¢ per successful call, which is $3.00 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 profile 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 Profile Scraper API endpoints

TikTok Profile

Facebook Profile

Instagram Profile

Instagram Basic Profile

More Threads scrapers

All Threads endpoints

Threads User Posts Threads Post 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