Threads · Search and trends

Threads Search Scraper API

The Threads Search endpoint is one API call: send a search query with your HProxy key and get back a clean, structured JSON object. Run any Threads keyword search and get the ranked posts back as JSON, with author and engagement counts on each. 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

ThreadsYouTubeRedditGooglePinterestTikTokInstagram

The call

One GET, and the search 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?query=coffee" \
  -H "X-API-Key: hpx_your_key_here"
Response200 OK · JSON
{
  "query": "your query",
  "results": [
    { "type": "video", "id": "72901...", "title": "...", "stats": { "views": 12043 } }
  ],
  "cursor": "eyJwYWdlIjoyfQ"
}

What comes back

The Threads search object.

results[]
Ranked results in the platform's own order.
type
Result type (user, video, post, product) per item.
query
The query the ranking was computed for.

What it takes

Parameters.

querystringRequiredcoffee

Search term or keyword.

start_datestring2026-07-01

Filter by date, as YYYY-MM-DD.

end_datestring2026-07-01

Filter by date, as YYYY-MM-DD.

trimbooleantrue

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

How it works

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

  • Monitor Threads for brand mentions, keywords or new competitors.
  • Build a trend-tracking pipeline off live search results.
  • Discover creators or products around any query.

Threads search questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Threads Search endpoint with a search query and your HProxy API key. Run any Threads keyword search and get the ranked posts back as JSON, with author and engagement counts on each. 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 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
YouTube Search13 endpoints on YouTubeReddit Search5 endpoints on RedditGoogle Search Results4 endpoints on GooglePinterest Search4 endpoints on PinterestTikTok Keyword Search23 endpoints on TikTokInstagram Reels Search11 endpoints on Instagram

More from Threads

5 Threads endpoints, one key.

The Threads catalog
Threads Search UsersSearch 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 API

What the Threads Search endpoint returns

Run any Threads keyword search and get the ranked posts back as JSON, with author and engagement counts on each. The JSON object carries results[], type and query. Nothing is summarised away on our side, so what you read in the response is what the Threads search page itself holds.

What you send to the Threads Search API

The call takes a search query. Required: query. Optional: start_date, end_date and trim. 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: YouTube Search, Reddit Search, Google Search Results, Pinterest Search, TikTok Keyword Search and Instagram Reels 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 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