§ The Twitter / X hub
Twitter / X

Twitter / X
scraper.

No proxy needed. 6 pre-built endpoints, parsed JSON in seconds.

6 endpoints·From $0.003 per call·Median under 2s
§ One call

Send a handle.
Get back JSON.

The profile scraper takes one input: handle. The response carries every public field Twitter / X exposes.

Request
cURL
curl https://api.hproxy.com/v1/scrape/twitter/profile/collect/by/handle \
  -H "Authorization: Bearer $HPROXY_KEY" \
  -H "Content-Type: application/json" \
  -d '{"handle":"Austen"}'
POST // 1 call · $0.0030 · <2s
Response200 OK
{
  "__typename": "User",
  "id": "VXNlcjoyMjE4MzgzNDk=",
  "rest_id": "221838349",
  "is_blue_verified": true,
  "legacy": {
    "created_at": "Wed Dec 01 19:13:23 +0000 2010",
    "description": "CEO https://t.co/m6TigM5azr & https://t.co/NuPTghEZ1I (part of @bloomtech)…",
    "followers_count": 377608,
    "friends_count": 1051,
    "location": "Austin, TX",
    "name": "Austen Allred",
    "profile_image_url_https": "https://pbs.twimg.com/profile_images/….jpg",
    "screen_name": "Austen",
    "statuses_count": 46114,
    "verified": false
  }
}
What comes backparsed fields
Twitter / X Profile
twitter_profile
created_atstring
descriptionstring
followers_countnumber
friends_countnumber
locationstring
namestring
profile_image_url_httpsurl
One real call · one structured record
§ Coverage

What you can
actually pull.

§ 01

Profiles

Bio, follower and following counts, post totals, verified flag, links, and the profile image — every public field the platform exposes about an account.

§ 02

Users

Public user objects with handle, display name, follower counts, and the profile image.

§ 03

Tweets

Tweet objects with full text, like, reply, retweet, quote and bookmark counts, language, and the author reference.

§ 04

Transcripts

AI-fallback transcript of any video — audio-to-text when no caption exists, the published captions otherwise.

§ 05

Community

Structured community objects returned as flat, predictable JSON — ready to drop straight into your database.

§ Every endpoint

The full list.
Prices included.

Every line is a live endpoint. Click through for the input schema, response shape, and the curl recipe.

§ What people build

One Twitter / X scraper.
Many shapes of work.

§ 01

Audience & creator discovery

Build lead and creator-discovery pipelines from Twitter / X public profiles. Filter by follower count, engagement, and region. The JSON is flat enough to drop into a Postgres column without normalisation.

§ 02

Brand & trend monitoring

Track every public post mentioning a brand or keyword across Twitter / X. Pipe captions into sentiment models and chart engagement over time without writing a single parser.

§ 03

AI training data

Feed clean, structured Twitter / X JSON straight into your model fine-tuning pipeline. Same schema every call — no scraping infrastructure to maintain.

§ 04

Dashboards & reporting

Wire Twitter / X signals into internal dashboards. One API key, predictable JSON, dollar-denominated pricing — finance can reason about the bill.

§ Questions

The honest
answers.

The questions that come up before the first call. If yours isn’t here, the founder reads support email himself — just write in.

Do I need proxies to use the Twitter / X scraper?

No. Every endpoint runs on our residential pool — fifty million IPs sourced through opt-in partner SDKs. You send an HTTP request with your API key; rotation, retries, and anti-bot handling are ours to worry about.

How does HProxy get past Twitter / X’s rate limits and bot detection?

Each call is routed through a residential session that matches typical organic traffic patterns. We don’t advertise specifics; what matters is the result — a 99%+ success rate on public-data endpoints in real customer traffic.

What does the JSON response look like?

Every endpoint returns a flat top-level wrapper (platform, scraper, data, creditsUsed, elapsedMs, requestId) with the parsed Twitter / X entity inside data. See the live example near the top of this page for the exact shape.

Is scraping public Twitter / X data legal?

Public data scraping (no login, no private content, no PII beyond what twitter.com itself publishes) sits within the boundaries set by hiQ Labs v. LinkedIn and similar US/EU precedents. We don’t serve endpoints that touch authenticated content. You’re responsible for your own use of the data under your local data-protection law (GDPR, CCPA, etc.).

What does each call cost?

From $0.003 per call on the standard endpoints. Endpoints that do heavier upstream work — AI transcripts, posts with media archived to R2 — cost more. The exact per-call price shows on each endpoint row below. One call = one charge, never multiplied by record count.

Can I test before signing up?

Yes — the wallet starts with a $2 deposit that’s refundable for 24 hours. That’s plenty of calls to verify the response shape matches what you’re building across all 6 Twitter / X endpoints.

How fast are the responses?

Median response time across the Twitter / X endpoints is under 2 seconds. Heavier endpoints (deep comment threads, cursor-paginated lists) can run 4-8 seconds depending on the page depth requested.

§ Try it

Two dollars,
first run.

Sign in with Google, drop $2 in the wallet, fire your first Twitter / X call against twitter.com. If it doesn’t do what you need, the balance is refundable for 24 hours.