Threads · Profiles

Threads Profile Scraper API

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.
Get your API keyThreads API reference
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes an account handle
  • Errors and timeouts are not charged

On Threads

Profiles1Posts and media2Search and trends2

Profiles

ThreadsTikTokFacebookInstagramLinkedInTwitter / XTwitchBlueskyTruth SocialSnapchatLinkmeYouTubeRedditSpotifyKomiLinkbioLinktreePillarSoundCloud

The call

One GET, and the profile comes back as JSON.

Your key goes in one header. 1 required parameter, and the answer is the object below it.

The full reference
curl "https://hproxy.com/api/v1/scrape/threads/profile?handle=zuck" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · 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"
}

What comes back

The Threads profile object.

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.

What it takes

Parameters.

handlestringRequiredzuck

Account handle or @username.

trimbooleantrue

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

cache_max_agestring1d

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`.

How it works

Scraping Threads profile, in three steps.

You write one line. Proxies, anti-bot walls, rendering and parsing happen on our side.

Create a free accountEvery Threads endpoint
  1. 1

    Create a free account

    Sign up and top up any amount. The balance pays for every HProxy product.
  2. 2

    Grab your API key

    One key from the dashboard authenticates every scraper.
  3. 3

    Call the endpoint

    Send the GET you need and read the JSON. That is the entire integration.

What people build with it

Where the Threads profile endpoint earns its keep.

  • 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 questions

Answered before you ask.

The reference

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.

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.

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.

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.

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.

Docs and AI

Connect your scraper to an AI, any time.

The whole Scraper API is published as markdown, so an assistant reads every endpoint, every parameter and a real response without a key and writes your integration. And because a scrape is one GET that answers in JSON, an agent can run the scraper itself, on its own schedule, with your key.

Read the scraper docsSet up your assistant

Claude, ChatGPT, Cursor, Gemini, Copilot, Windsurf, Perplexity, Ollama and any assistant that speaks MCP.

The API as markdown

Paste /llms/scraper-api.txt into Claude, ChatGPT, Cursor or Copilot: every endpoint and the whole catalog, in one file. No key and no account to read it.

Open the markdown

An agent can call it

One GET with your key returns structured JSON, so an agent scrapes on its own schedule. No browser to drive, no parser to keep alive between runs.

See the endpoints

MCP server and CLI

Built by us for the free tools and hosted at mcp.hproxy.com: the proxy list, the checker and the IP lookup as tools in Claude, ChatGPT, Cursor or any assistant that speaks MCP. Nothing to install, no key.

Add it to your assistant

API docs

Every scraper endpoint documented end to end, with the parameters it takes and the response it really returns.

Read the docs

Profiles elsewhere

The same data on 18 other platforms.

One key, one JSON shape, one balance. Move sideways without learning a second API.

Profile Scraper API
TikTok Profile23 endpoints on TikTokFacebook Profile17 endpoints on FacebookInstagram Profile11 endpoints on InstagramLinkedIn Profile6 endpoints on LinkedInTwitter / X Profile6 endpoints on Twitter / XTwitch Profile4 endpoints on TwitchBluesky Profile3 endpoints on BlueskyTruth Social Profile3 endpoints on Truth SocialSnapchat Profile1 endpoint on SnapchatLinkme Profile1 endpoint on LinkmeYouTube Channel13 endpoints on YouTubeReddit Subreddit Details5 endpoints on RedditSpotify Artist3 endpoints on SpotifyKomi Page1 endpoint on KomiLinkbio Page1 endpoint on LinkbioLinktree Page1 endpoint on LinktreePillar Page1 endpoint on PillarSoundCloud Artist1 endpoint on SoundCloud

More from Threads

5 Threads endpoints, one key.

The Threads catalog
Threads User PostsPosts and mediaThreads PostPosts and mediaThreads SearchSearch and trendsThreads Search UsersSearch and trends

Every platform

The same key works on all 23.

The whole catalog

More on the Threads Profile API

What the Threads Profile endpoint returns

Pull a public Threads profile from a handle: bio, follower count, verification and the links on the profile. The JSON object carries bio / links, counts, isVerified and avatar. Nothing is summarised away on our side, so what you read in the response is what the Threads profile page itself holds.

What you send to the Threads Profile API

The call takes an account handle. Required: handle. Optional: trim and cache_max_age. Your key travels in the X-API-Key header, the response is JSON, and the call is billed at 0.15¢, $1.49 per 1,000.

Profiles on other platforms

The same profiles data is available on 18 other platforms: TikTok Profile, Facebook Profile, Instagram Profile, LinkedIn Profile, Twitter / X Profile, Twitch Profile, Bluesky Profile, Truth Social Profile, Snapchat Profile, Linkme Profile, YouTube Channel, Reddit Subreddit Details, Spotify Artist, Komi Page, Linkbio Page, Linktree Page, Pillar Page and SoundCloud Artist. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from Threads to another network is a change of URL rather than a second integration.

Is scraping Threads profile allowed?

The endpoint reads publicly available Threads data, the same pages anyone can open in a browser without logging in. It does not touch private accounts or anything behind a password. How you then use the data is yours to keep lawful, under the rules that apply to you and to Threads.

Ready when you are.

Your dashboard is ten seconds away. No sales call, no subscription, no minimum.

Get startedSee every scraperTalk to us