Web scrapers

Post Scraper API

The largest group in the catalog, and the one most people mean when they say scraping. These endpoints return published content two ways: one post resolved from its URL, or a creator's feed walked page by page with a cursor. Videos, reels, shorts, tweets, photos, tracks, albums, pins and live status all resolve to the same core object of caption, media, author, timestamp and engagement, with the platform's own extras left intact rather than flattened away.

Get your API key Every scraper

40 endpoints
14 platforms
from $1.49 per 1,000 calls
One key, one JSON shape

Post Scraper API

40 endpoints across 14 platforms.

Single posts by URL, or a creator's whole feed, page by page.

In every response

The same JSON, whichever platform you ask.

id / url Stable post identifier and its canonical link.
caption / text The post body exactly as published, emoji and line breaks kept.
media[] Direct media URLs at each resolution the platform serves.
author Handle, ID and avatar of the account that published it.
engagement View, like, comment and share counts where the platform exposes them.
cursor Pagination token on the feed endpoints, for walking past the first page.

curl "https://hproxy.com/api/v1/scrape/twitter/tweets?handle=nasa" \
  -H "X-API-Key: hpx_your_key_here"

Response · Twitter / X User Tweets200 OK · JSON

{
  "id": "1889...",
  "text": "shipped it. took four days.",
  "author": { "username": "@handle", "followerCount": 90421 },
  "stats": { "replies": 84, "reposts": 312, "likes": 4120, "views": 291043 },
  "media": [ { "type": "photo", "url": "https://.../img.jpg" } ],
  "quoted": null
}

What people build with it

Where post scraper api earns its keep.

Archive a creator's back catalogue with the media URLs and the engagement attached.
Track how a campaign hashtag or a product mention performs across platforms.
Feed a recommendation or trend model with real published content instead of a sample.
Monitor a competitor's posting cadence and what actually lands for them.

Post Scraper API questions

Answered before you ask.

The scraper docs

Yes, through the feed endpoints. Each call returns one page plus a cursor, and you keep passing the cursor back until it comes back empty. How deep the history goes is set by the platform, not by us.

A single-post endpoint takes one URL and returns the full object for that post, including the fields a feed listing omits. A feed endpoint takes an account and returns many posts in a lighter shape. Use the feed to discover, then the single post where you need depth.

You get direct media URLs in the response. Downloading the bytes is your call and happens outside the API, so you only pay for the extraction, not for the transfer.

No. These endpoints read what is publicly live at the moment of the call. Once a platform removes a post there is nothing public left to read.

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