§ 01
Audience & creator discovery
Build lead and creator-discovery pipelines from Threads public profiles. Filter by follower count, engagement, and region. The JSON is flat enough to drop into a Postgres column without normalisation.
§ The Threads hub
Threads
scraper.
No proxy needed. 5 pre-built endpoints, parsed JSON in seconds.
5 endpoints·From $0.003 per call·Median under 2s
§ One call
Send a handle.
Get back JSON.
The profile scraper takes one input: handle. The response carries every public field Threads exposes.
Request
cURL
curl https://api.hproxy.com/v1/scrape/threads/profile/by/handle \
-H "Authorization: Bearer $HPROXY_KEY" \
-H "Content-Type: application/json" \
-d '{"handle":"trendspider"}'POST // 1 call · $0.0030 · <2s
Response200 OK
{
"success": true,
"pk": "63496592589",
"username": "sportsillustrated",
"full_name": "Sports Illustrated",
"biography": "Sports, sports and more sports.",
"follower_count": 551296,
"is_verified": true,
"profile_pic_url": "https://scontent-atl3-2.cdninstagram.com/v/t51.2885-19/….jpg"
}What comes backparsed fields
Threads Profile
threads_profile
pkstring
usernamestring
full_namestring
biographystring
follower_countnumber
is_verifiedboolean
profile_pic_urlurl
One real call · one structured record
§ Coverage
What you can
actually pull.
§ 01
Profiles
Bio, follower and following counts, post totals, verified flag, links, and the profile image — every public field the platform exposes about an account.
§ 02
Posts
Full post objects: caption text, like and comment counts, view counts, media URLs, and timestamps — pulled by handle or by direct URL.
§ 03
Search
Keyword and query search results with the matched entities and the engagement metadata behind each one.
§ 04
Users
Public user objects with handle, display name, follower counts, and the profile image.
§ Every endpoint
The full list.
Prices included.
Every line is a live endpoint. Click through for the input schema, response shape, and the curl recipe.
Threads Profile
/v1/scrape/threads/profile/by/handle
Public Threads profile metadata.
$0.0030
per call
Threads User Posts
/v1/scrape/threads/user/posts/by/handle
Recent posts from a public Threads user.
$0.0030
per call
Threads Post
/v1/scrape/threads/post/by/url
Single Threads post by URL with engagement.
$0.0030
per call
Threads Search
/v1/scrape/threads/search/by/keyword
Search public Threads posts by keyword.
$0.0030
per call
Threads Search Users
/v1/scrape/threads/search/users/by/keyword
Search for Threads users by username keyword.
$0.0030
per call
§ What people build
One Threads scraper.
Many shapes of work.
§ 02
Brand & trend monitoring
Track every public post mentioning a brand or keyword across Threads. Pipe captions into sentiment models and chart engagement over time without writing a single parser.
§ 03
Search & hashtag intelligence
Query Threads by keyword or hashtag and get back the matched entities with their engagement metadata attached. Power competitive research and content-gap analysis.
§ 04
AI training data
Feed clean, structured Threads JSON straight into your model fine-tuning pipeline. Same schema every call — no scraping infrastructure to maintain.
§ Questions
The honest
answers.
The questions that come up before the first call. If yours isn’t here, the founder reads support email himself — just write in.
Do I need proxies to use the Threads scraper?
No. Every endpoint runs on our residential pool — fifty million IPs sourced through opt-in partner SDKs. You send an HTTP request with your API key; rotation, retries, and anti-bot handling are ours to worry about.
How does HProxy get past Threads’s rate limits and bot detection?
Each call is routed through a residential session that matches typical organic traffic patterns. We don’t advertise specifics; what matters is the result — a 99%+ success rate on public-data endpoints in real customer traffic.
What does the JSON response look like?
Every endpoint returns a flat top-level wrapper (platform, scraper, data, creditsUsed, elapsedMs, requestId) with the parsed Threads entity inside data. See the live example near the top of this page for the exact shape.
Is scraping public Threads data legal?
Public data scraping (no login, no private content, no PII beyond what threads.net itself publishes) sits within the boundaries set by hiQ Labs v. LinkedIn and similar US/EU precedents. We don’t serve endpoints that touch authenticated content. You’re responsible for your own use of the data under your local data-protection law (GDPR, CCPA, etc.).
What does each call cost?
From $0.003 per call on the standard endpoints. Endpoints that do heavier upstream work — AI transcripts, posts with media archived to R2 — cost more. The exact per-call price shows on each endpoint row below. One call = one charge, never multiplied by record count.
Can I test before signing up?
Yes — the wallet starts with a $2 deposit that’s refundable for 24 hours. That’s plenty of calls to verify the response shape matches what you’re building across all 5 Threads endpoints.
How fast are the responses?
Median response time across the Threads endpoints is under 2 seconds. Heavier endpoints (deep comment threads, cursor-paginated lists) can run 4-8 seconds depending on the page depth requested.
§ Try it
Two dollars,
first run.
Sign in with Google, drop $2 in the wallet, fire your first Threads call against threads.net. If it doesn’t do what you need, the balance is refundable for 24 hours.