Social Media

X (Twitter) Scraper API

Public X/Twitter profiles, posts and engagement - real-time conversation and brand signals.

From $15/mo · 1,000 free API calls to start · see pricing

BOOK A SCOPING CALL ALL READY APIS
scrapeguys · x-twitter · sample response
{ "source": "x", "handle": "@brand", "followers": 95000, "posts_30d": 64, "avg_engagement": "1.1%", "mentions_30d": 2140 }
What you can extract

Structured, ready to use

  • Profiles & follower metrics
  • Posts & threads
  • Engagement counts
  • Keyword & cashtag tracking
  • Reply sentiment inputs
  • Competitor share of voice
Example schema
FieldTypeExample
sourcestring"x"
handlestring"@brand"
followersnumber95000
posts_30dnumber64
avg_engagementstring"1.1%"
mentions_30dnumber2140

The full schema is customized to your workflow on the scoping call.

example request · async jobs API
curl -X POST https://api.scrapeguys.com/v1/jobs \
  -H "X-API-Key: $SCRAPEGUYS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"target": "x", "params": {"profile": "nasa", "fields": ["followers", "recent_posts"]}}'

Illustrative request - field names and params for your deployment are fixed on the scoping call and documented in your workspace. Full request/response reference: API docs.

Use cases

What teams build on this

Creator & brand tracking

Profiles, content and engagement at scale.

Trend & sentiment models

Clean feeds for AI and trend detection.

Competitive social intel

Posting cadence, formats and engagement benchmarks.

Guides & answers: Social data Q&A · What is a web scraping API?

How it works

Scoped, built and operated for you

1

Scoping call

Fields, cadence, geography - shaped to your workflow. Docs & samples shared here.

2

We operate it

Anti-bot, proxies, parsing, monitoring - managed and SLA-backed on our side.

3

Clean JSON in

Async job API, BI feed, dashboard or MCP - one schema, your stack.

FAQ

Frequently asked questions

Do you scrape private accounts?
No. Public profiles and public content only - no logged-in scraping of private accounts, no personal data harvesting. Coverage is scoped per platform and per use case before anything goes live.
What signals do you capture?
Profiles and follower metrics, posts and content metadata, engagement counts, hashtags, sounds and posting cadence - scoped per platform. Enough to compute share of voice, engagement benchmarks and creator rankings without you touching a scraper.
Can this feed creator discovery or trend models?
Yes. The same feeds power creator discovery, brand-safety screening and trend detection - clean, typed JSON lands in your warehouse or straight into your models on the cadence you choose.
How do I get the API documentation and a data sample?
API documentation is public at scrapeguys.com/docs - request format, response schemas, status codes and worked examples. For a sample dataset on your exact targets, book a short scoping call: each deployment is customized to your schema, fields and volumes, and most teams have a sample in hand within a day.
How fast can this go live for us?
A scoped deployment typically goes live as a production API in 48-72 hours. That includes the scraper itself, a wrapper API shaped to your workflow, custom fields added to the response, monitoring and alerting on our side, and a staging key so your team can validate the schema before production traffic starts.
How is the data delivered - do we have to integrate an API?
An API is one option, not a requirement. The same data layer ships as REST JSON APIs with async jobs and webhooks, scheduled exports into Power BI, Looker, Snowflake, BigQuery or Google Sheets, a white-label dashboard your team signs into with zero integration, or MCP tools your AI agents call live. You can mix channels - API for engineering, dashboard for the commercial team - on one deployment.
What happens when the target site changes or a scrape fails?
That is our problem, not yours. Every source is monitored around the clock - layout changes, anti-bot updates and success-rate drops page our engineers before they page you, and your field names stay stable through redesigns because we absorb the change behind the schema. Failed requests are retried automatically, and anything that still fails is not billed: pricing is success-based.

Need X (Twitter) data in production?

A 20-minute scoping call gets you documentation, samples and a timeline - most deployments are live in 48-72 hours.

BOOK A CALL SEND YOUR TARGETS