Threads · Search and trends

Threads Search Users Scraper API

The Threads Search Users endpoint is one API call: send a search query with your HProxy key and get back a clean, structured JSON object. Search Threads accounts by keyword and get ranked profiles back with handle, display name, follower count and verification. 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 a search query
  • Errors and timeouts are not charged

On Threads

Profiles1Posts and media2Search and trends2

Search and trends

ThreadsTikTokYouTubeInstagramRedditGooglePinterest

The call

One GET, and the search users 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/search-users?query=coffee" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · JSON
{
  "query": "your query",
  "users": [
    { "username": "@handle", "displayName": "Real Name",
      "followerCount": 90421, "isVerified": true }
  ],
  "cursor": "eyJwYWdlIjoyfQ"
}

What comes back

The Threads search users object.

users[]
Ranked matching accounts with handle and display name.
followerCount
Audience size per result, so you can filter.
isVerified
Verification flag per result.

What it takes

Parameters.

querystringRequiredcoffee

Search term or keyword.

How it works

Scraping Threads search users, 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 search users endpoint earns its keep.

  • Build creator shortlists filtered by audience size.
  • Find and verify accounts for outreach at scale.
  • Enrich a lead list with live Threads handles.

Threads search users questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Threads Search Users endpoint with a search query and your HProxy API key. Search Threads accounts by keyword and get ranked profiles back with handle, display name, follower count and verification. 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 search users 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

Search and trends elsewhere

The same data on 6 other platforms.

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

Search API
TikTok Search Users23 endpoints on TikTokYouTube Search13 endpoints on YouTubeInstagram Reels Search11 endpoints on InstagramReddit Search5 endpoints on RedditGoogle Search Results4 endpoints on GooglePinterest Search4 endpoints on Pinterest

More from Threads

5 Threads endpoints, one key.

The Threads catalog
Threads SearchSearch and trendsThreads ProfileProfilesThreads User PostsPosts and mediaThreads PostPosts and media

Every platform

The same key works on all 23.

The whole catalog

More on the Threads Search Users API

What the Threads Search Users endpoint returns

Search Threads accounts by keyword and get ranked profiles back with handle, display name, follower count and verification. The JSON object carries users[], followerCount and isVerified. Nothing is summarised away on our side, so what you read in the response is what the Threads search users page itself holds.

What you send to the Threads Search Users API

The call takes a search query. Required: query. 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.

Search and trends on other platforms

The same search and trends data is available on 6 other platforms: TikTok Search Users, YouTube Search, Instagram Reels Search, Reddit Search, Google Search Results and Pinterest Search. 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 search users 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