Twitter / X · Posts and media

Twitter / X Tweet Scraper API

The Twitter / X Tweet endpoint is one API call: send a URL with your HProxy key and get back a clean, structured JSON object. Pull a single X post from its URL: full text, media, the quote and reply chain around it, and reply, repost, like and view 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 Twitter / X changes its markup. You only ever touch the JSON.
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes a URL
  • Errors and timeouts are not charged

The call

One GET, and the tweet 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/twitter/tweet?url=https%3A%2F%2Ftwitter.com%2Fnasa%2Fstatus%2F1745510925348782269" \
  -H "X-API-Key: hpx_your_key_here"
Response200 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 comes back

The Twitter / X tweet object.

text
Full post text with entities resolved.
stats
Replies, reposts, likes, bookmarks and views.
media[]
Attached images and video with direct URLs.
quoted / inReplyTo
The quote and reply chain around it.

What it takes

Parameters.

urlurlRequiredhttps://twitter.com/nasa/status/1745510925348782269

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 Twitter / X tweet, in three steps.

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

  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 Twitter / X tweet endpoint earns its keep.

  • Archive posts before they are edited or deleted.
  • Track how a narrative spreads through quotes and replies.
  • Feed a monitoring tool with full post objects.

Twitter / X tweet questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Twitter / X Tweet endpoint with a URL and your HProxy API key. Pull a single X post from its URL: full text, media, the quote and reply chain around it, and reply, repost, like and view 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 Twitter / X data, the same pages anyone can open in a browser. You are responsible for using the data in line with applicable laws and Twitter / X's terms for your use case.

A structured JSON object with the full tweet data Twitter / X 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.

More on the Twitter / X Tweet API

What the Twitter / X Tweet endpoint returns

Pull a single X post from its URL: full text, media, the quote and reply chain around it, and reply, repost, like and view counts. The JSON object carries text, stats, media[] and quoted / inReplyTo. Nothing is summarised away on our side, so what you read in the response is what the Twitter / X tweet page itself holds.

What you send to the Twitter / X Tweet API

The call takes a URL. Required: url. 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.

Posts and media on other platforms

The same posts and media data is available on 13 other platforms: TikTok Video, Facebook Profile Reels, YouTube Channel Videos, Instagram Post, LinkedIn Company Posts, Reddit Subreddit Posts, Threads User Posts, Pinterest Pin, Twitch User Videos, Bluesky User Posts, Spotify Track, Truth Social User Posts and Kick Clip. They share this endpoint's JSON shape, its per-call billing and your one API key, so moving from Twitter / X to another network is a change of URL rather than a second integration.

Is scraping Twitter / X tweet allowed?

The endpoint reads publicly available Twitter / X 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 Twitter / X.

Ready when you are.

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