Social Media · Twitter / X Scraper
Twitter / X Community Scraper API
Pull an X Community in full: name, description, member count, moderators and the rules it is run under. No headless browsers, no captchas, proxies included.
// Twitter / X · Community
curl -H "X-API-Key: hpx_your_key_here" \
"https://hproxy.com/api/v1/scrape/twitter/community?url=https%3A%2F%2Ftwitter.com%2Fnasa%2Fstatus%2F1745510925348782269"
// → { "data": { … }, "records": 1, "costUsd": … }
From Request to Clean JSON
You write one line. We do everything between the request and the data.
You send
One API call
GET the Twitter / X endpoint with your key. That's all your code does.
We handle
Proxies · captchas · parsing
Residential exit, anti-bot walls, JS rendering and extraction, all server-side, on us.
You get
Clean JSON
A structured object every time. No HTML, no scraping code, no maintenance.
The Twitter / X Community endpoint is one API call: send a URL with your HProxy key and get back a clean, structured JSON object. Pull an X Community in full: name, description, member count, moderators and the rules it is run under. 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.
What the Twitter / X Community API returns
name / description
Community name, description and topic.
memberCount
Total members and active members where exposed.
rules[]
Posted community rules.
createdAt
When the community was created.
Example response
{
"name": "Community name",
"description": "What the community is for.",
"memberCount": 412003,
"rules": [ { "position": 1, "title": "Be civil" } ],
"createdAt": "2013-06-11"
}Trimmed for brevity. Every call returns the full object with all fields listed here.
The Twitter / X community endpoint
Full Twitter / X reference →/api/v1/scrape/twitter/communityParameters
urlurlrequiredTarget URL (profile, post or video).
trimbooleanoptionalReturn a slimmed-down payload (drops verbose fields).
Example request
curl "https://hproxy.com/api/v1/scrape/twitter/community?url=https%3A%2F%2Ftwitter.com%2Fnasa%2Fstatus%2F1745510925348782269" \
-H "X-API-Key: hpx_your_key_here"POST with a JSON body works too. Failed calls, timeouts and rate-limited calls are never billed.
Scraping Twitter / X community in three steps
Create a free account
Sign up and top up any amount. The balance pays for every HProxy product and never expires.
Grab your API key
One key from the dashboard authenticates every scraper, Twitter / X community included.
Call the endpoint
Send the target to the Twitter / X Community endpoint and read the JSON. That is the whole integration.
No captchas, ever
Anti-bot walls, JS rendering and rate limits are handled server-side. You call an API, that is the whole job.
Residential-backed
Every request exits through HProxy's own residential network, so it looks like a real user on a real device.
Pay per call
No subscription, no seat licenses. Calls are billed from your balance and the balance never expires.
Fresh on every call
Responses are scraped live at request time, no stale cache dressed up as data.
Failures are free
Automatic retries first; if an extraction still fails, the call is not charged.
Scales with you
From one call to millions: same endpoint, same price curve, volume discounts as you grow.
What people build with it
Size a community before investing in it.
Monitor rule changes and moderation shifts.
Find the communities where your niche actually talks.
Twitter / X Community pricing
$3.00
per 1,000 calls · 0.3¢ each
Pay per call, no subscription
Failed extractions are not charged
Proxies included in the price