X (Twitter) scraper API
Look up public X profiles, posts, replies, communities, and search results without rebuilding auth and rate-limit wrappers every time the platform changes.
9 endpointsWhy teams use Social Fetch for X (Twitter)
X's official API tiers and product packaging change often enough that teams treat Twitter access as a procurement problem, not an engineering one. Many products only need public profile cards, recent posts, or keyword search — not elevated access or write scopes.
Social Fetch exposes those public lookups as `GET /v1/twitter/...` routes under the same key as TikTok and Instagram. Paths use handle-style parameters familiar to anyone who has integrated other Social Fetch profile routes.
Search and community routes sit alongside profile fetches so monitoring jobs can fan out without a second vendor.
What X (Twitter) data can you get?
- Profile by handle with public bio and metrics.
- Tweet / post detail and reply threads.
- User timeline-style post lists where documented.
- Keyword search for monitoring and research.
- Community metadata for niche tracking.
X (Twitter) API endpoints
Grouped by capability from the live API catalog. Open an endpoint page for parameters and examples — credit notes come from OpenAPI pricing extensions.
Profiles & channels
2Lists & graphs
2Content
1Search & discovery
2Comments
1Transcripts
1How to call the X (Twitter) API
1. Sign up and copy a key
Create a Social Fetch account. Free credits are enough to verify a profile GET and a search call before buying a pack.
2. Call `/v1/twitter/...`
Start with `GET /v1/twitter/profiles/{handle}`. Add search or post routes as your job requires. Send `x-api-key` on every request.
3. Handle statuses explicitly
Use `lookupStatus` for missing or private accounts. Retry only on documented transient errors — not on not-found.
How much does the X (Twitter) API cost?
X routes use credit pricing documented per operation. Some search routes cost more than a single profile GET — read the operation page. `meta.creditsCharged` confirms what ran.
Social Fetch vs the official X (Twitter) API
X's official API is the right choice when you need elevated access, posting, or compliance products tied to X's own contracts. Social Fetch is for public-data enrichment: no X developer app required, credit-metered, same envelope as the rest of our marketplace.
X (Twitter) API FAQ
Is there an X / Twitter scraper API?
Yes. Social Fetch provides REST endpoints for public X profiles, posts, replies, communities, and search.
Do I need an X developer account?
Not for Social Fetch routes. You only need a Social Fetch API key.
What X data can I fetch?
Profiles, tweets/posts, replies, communities, and search — see the endpoint grid on this page for paths and docs.
How much does the Twitter API cost here?
Credits per successful lookup. Pack pricing is on `/pricing`; per-route notes are in the API reference.
Can I search X posts by keyword?
Yes — search routes are part of the Twitter tag in the catalog. Check docs for query parameters and credit cost.
X API vs Social Fetch — when to pick which?
Pick X official when your contract with X requires it or you need write/elevated products. Pick Social Fetch for public lookups alongside other social networks on one key.
Does this work for private accounts?
Private content is not returned as fake public data. Expect typed lookup outcomes for inaccessible accounts.
Is scraping X allowed?
We return publicly visible data. Your use must comply with X's terms and the law in your jurisdiction.
Start with X (Twitter) data
Create an account, spend the 100 free credits on live X (Twitter) routes, then buy a pack when the JSON fits your pipeline. Credits do not expire on pay-as-you-go packs.