Twitter / X · Posts and media

Twitter / X User Tweets Scraper API

The Twitter / X User Tweets endpoint is one API call: send an account handle with your HProxy key and get back a clean, structured JSON object. Pull an X account's timeline, page by page, with full text, media, and reply, repost, like and view counts on each post. 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.
Get your API keyTwitter / X API reference
  • 0.15¢ per call
  • $1.49 per 1,000
  • Takes an account handle
  • Errors and timeouts are not charged

On Twitter / X

Profiles2Posts and media3Transcripts1

Posts and media

Twitter / XTikTokFacebookYouTubeInstagramLinkedInRedditThreadsPinterestTwitchBlueskySpotifyTruth SocialKick

The call

One GET, and the user tweets 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/tweets?handle=nasa" \
  -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 user tweets 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.

handlestringRequirednasa

Account handle or @username.

trimbooleantrue

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

How it works

Scraping Twitter / X user tweets, in three steps.

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

Create a free accountEvery Twitter / X 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 Twitter / X user tweets 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 user tweets questions

Answered before you ask.

The reference

Send one authenticated HTTPS request to the Twitter / X User Tweets endpoint with an account handle and your HProxy API key. Pull an X account's timeline, page by page, with full text, media, and reply, repost, like and view counts on each post. 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 user tweets 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.

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

Posts and media elsewhere

The same data on 13 other platforms.

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

Post Scraper API
TikTok Video23 endpoints on TikTokFacebook Profile Reels17 endpoints on FacebookYouTube Channel Videos13 endpoints on YouTubeInstagram Post11 endpoints on InstagramLinkedIn Company Posts6 endpoints on LinkedInReddit Subreddit Posts5 endpoints on RedditThreads User Posts5 endpoints on ThreadsPinterest Pin4 endpoints on PinterestTwitch User Videos4 endpoints on TwitchBluesky User Posts3 endpoints on BlueskySpotify Track3 endpoints on SpotifyTruth Social User Posts3 endpoints on Truth SocialKick Clip1 endpoint on Kick

More from Twitter / X

6 Twitter / X endpoints, one key.

The Twitter / X catalog
Twitter / X TweetPosts and mediaTwitter / X Community TweetsPosts and mediaTwitter / X ProfileProfilesTwitter / X Tweet TranscriptTranscriptsTwitter / X CommunityProfiles

Every platform

The same key works on all 23.

The whole catalog

More on the Twitter / X User Tweets API

What the Twitter / X User Tweets endpoint returns

Pull an X account's timeline, page by page, with full text, media, and reply, repost, like and view counts on each post. 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 user tweets page itself holds.

What you send to the Twitter / X User Tweets API

The call takes an account handle. Required: handle. Optional: 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.

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 user tweets 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.

Get startedSee every scraperTalk to us