Threads · Posts and media

Threads Post Scraper API

The Threads Post endpoint is one API call: send a URL with your HProxy key and get back a clean, structured JSON object. Pull a single Threads post from its URL: full text, attached media, author and its reply, repost and like counts. 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 key Threads API reference

0.15¢ per call
$1.49 per 1,000
Takes a URL
Errors and timeouts are not charged

On Threads

Profiles1Posts and media2Search and trends2

Posts and media

Threads

The call

One GET, and the post 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/post?url=https%3A%2F%2Fwww.threads.net%2F%40zuck" \
  -H "X-API-Key: hpx_your_key_here"

Response200 OK · JSON

{
  "posts": [
    { "id": "88120...", "text": "we just shipped something big",
      "author": { "username": "@handle" },
      "media": [ { "type": "photo", "url": "https://.../img.jpg" } ],
      "stats": { "reactions": 4120, "comments": 214, "shares": 88 },
      "createdAt": "2026-07-28T11:04:00Z" }
  ],
  "cursor": "eyJwYWdlIjoyfQ"
}

What comes back

The Threads post object.

posts[]: Each post with text, media and permalink.
author: Poster handle, ID and display name.
stats: Reactions, comments and shares per post.
createdAt: Publish timestamp, so you can sort and dedupe.

What it takes

Parameters.

urlurlRequiredhttps://www.threads.net/@zuck

Target URL (profile, post or video).

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 post, in three steps.

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

Create a free account Every Threads endpoint

1
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product.
2
Grab your API key
One key from the dashboard authenticates every scraper.
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 post endpoint earns its keep.

Track everything an account publishes, automatically.
Feed a content archive or compliance record.
Benchmark posting cadence and engagement against rivals.

Threads post questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Threads Post endpoint with a URL and your HProxy API key. Pull a single Threads post from its URL: full text, attached media, author and its reply, repost and like counts. 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 post 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 docs Set 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