X (Twitter) scraper API. Every tweet, as JSON.
Profiles, tweets, replies, followers and search in one request. No developer account, no app approval and no X API tier to buy.
- No developer account
- Lists, communities and Spaces
- Batch profiles and posts
- Failed lookups aren't charged
Teams running monitoring, research, and enrichment pipelines
Why Social Fetch
We run the X (Twitter) scrapers. You build the product.
Live X (Twitter) data as JSON — proxies, platform changes and consistent output handled for you.
X (Twitter), plus every other network
One key and one response envelope for X (Twitter) and 24 more platforms — profiles, posts, search, comments and transcripts.
Pricing you can reason about
One request, one credit. Know how far your balance will go before you run your next batch.
Live data on every request
Fetch public data when you ask for it — not from a shared cache.
No scraper maintenance
We handle proxies, browser changes, and platform breakages.
Built for production jobs
Run concurrent workloads with explicit statuses and request IDs.
Regular jobs. Better rates.
Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.
What X (Twitter) data can you get?
29 endpoints, one API key. Every response comes back as live JSON in the same envelope.
Profiles & channels
Look up a X (Twitter) account by handle or URL — bio, counts and metadata.
Lists & graphs
Page through an account's posts, videos, followers and more.
+3 more lists & graphs endpointsContent
Fetch a single post or video by URL, with metrics and media.
+1 more content endpointsSearch & discovery
Search X (Twitter) by keyword, hashtag or trend.
Comments
Pull comment threads and replies for any public post.
Transcripts
Plain-text transcripts with timestamps for video content.
Other
More X (Twitter) routes on the same key.
+5 more other endpoints
Browse all 29 X (Twitter) endpoints
Profiles & channels
Lists & graphs
Content
Search & discovery
Comments
Transcripts
Other
What teams build with X (Twitter) data
Monitoring, enrichment, research and content workflows on X (Twitter) data — the same API as every other platform.
How it works
Your first request in three steps.
Use TypeScript or your automation tool of choice.
Sources
+ 19 more platforms
One request
GET/v1/tiktok/profiles/
x-api-key: sk_live_••••••••
Same JSON shape
{
"data": {
"lookupStatus": "found",
"profile": {
"platform": "tiktok",
"handle": "charlidamelio",
"displayName": "charli d’amelio",
"verified": true
},
"metrics": {
"followers": 160263648
}
}
}Step 1
Create your free account
Get an API key with 100 requests included.
Step 2
Choose an endpoint
Pass a username, URL, keyword, or post ID.
Step 3
Get clean JSON
Use the response immediately or send it into your pipeline.
Works with your stack
Code, automate, or connect your AI.
TypeScript
n8n
- Make
- Apify
- MCP
- AI clients
Pricing
Social data, priced simply.
Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.
Starter
18,000credits
$1.61 per 1k · $0.00161 per request
- Top up from $1.61 / 1k if you run out
- Up to 25 monitors
Growth
50,000credits
$1.58 per 1k · $0.00158 per request
- Top up from $1.58 / 1k if you run out
- 5 team seats
- Up to 100 monitors
Scale
150,000credits
$1.50 per 1k · $0.00150 per request
- Top up from $1.50 / 1k if you run out
- 25 team seats
- Up to 250 monitors
- Cancel anytime
- 30-day money-back guarantee
- Price locked while you stay
Need 1M+ credits, invoicing, or volume rates? Talk to us
Trust signals
DevHunt
Product Hunt
Uneed
Customers
Teams building on Social Fetch.
“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”
“Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”
“Live profile data on every request. We never flag accounts from a stale cache.”
“Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”
X (Twitter) API: common questions
Is there an X / Twitter API that doesn't require a developer account?
Yes. Social Fetch's nine Twitter routes read public profiles, timelines, single tweets, reply threads, video transcripts, search, hashtags, and communities over REST. You authenticate with a Social Fetch API key only — no X developer account, app approval, or OAuth.
What X / Twitter data can I pull with Social Fetch?
Profile cards (GET /v1/twitter/profiles/{handle}), handle timelines (.../tweets), single tweets by URL or id (GET /v1/twitter/tweets), reply threads (.../replies), video tweet transcripts (.../transcript), operator-first and hashtag search (GET /v1/twitter/search, GET /v1/twitter/hashtags), and community metadata plus community posts (GET /v1/twitter/communities, .../tweets). Exact parameters and response fields are on each endpoint page linked from this hub.
How do I fetch a single tweet by URL?
Call GET /v1/twitter/tweets with a required url query param — a tweet permalink (x.com or twitter.com /status/...) or a bare numeric id. Read data.lookupStatus, then data.tweet and data.author. Pass trim=true for a smaller payload that omits author and tweet core detail.
How do I list tweets for a handle?
Call GET /v1/twitter/profiles/{handle}/tweets. Optional params: limit (default 40, max 100), cursor, includeReplies (default false), and includePinned (default false, first page only). Page forward with data.page.nextCursor while data.page.hasMore is true.
Can I get replies to a specific tweet?
Yes. GET /v1/twitter/tweets/replies takes the same url (or numeric id) input as the single-tweet route and returns data.replies with conversationId / inReplyToStatusId linkage, cursor-paged the same way as profile tweets.
Can I get a transcript of a video tweet?
Yes, via GET /v1/twitter/tweets/transcript. data.transcript is a plain string when speech is detected, or null when it isn't — a found lookupStatus does not guarantee text. Videos that exceed the supported length return HTTP 400 video_too_long_for_transcription rather than a null string on 200.
What is the difference between Twitter search and hashtag search?
GET /v1/twitter/search is operator-first search — from:, OR, quotes, #hashtag, filter:, and -negation belong in query, and typed extras compile after it. GET /v1/twitter/hashtags is discovery for one specific tag. Both share the same section tabs (top, latest, people, photos, videos) and cursor pagination, but they are separate operations with separate credit charges — a #tag inside search is not the same call as the hashtag route.
What are X Communities, and can I pull their posts?
Communities are X's topic rooms, addressed by an x.com/i/communities/{id} permalink. GET /v1/twitter/communities returns the card — name, member count, joinPolicy (open or restricted), rules, and creator. GET /v1/twitter/communities/tweets pages the posts published inside. Both take the community URL, not a handle or hashtag.
What happens for private, suspended, or deleted accounts and tweets?
Social Fetch does not invent public data for inaccessible accounts or posts. Branch on data.lookupStatus (found, not_found, and related typed outcomes documented per route) before writing a row. A found profile can still page zero tweets under a restrictive filter, and a found community-tweets call can return an empty tweets array when the room has no matching posts — check the array length, not just the status.
How much does the Twitter API cost on Social Fetch?
1 credit per successful request, including profile cards, single tweets, transcripts, communities, handle timelines, search, hashtag search, and reply threads. Each paginated page is a separate billed call. Pack pricing is on /pricing; confirm the actual cost on every response with meta.creditsCharged.
The X (Twitter) API in detailHow the X (Twitter) routes work, what they cost, and how they differ from the official API.
Why teams use Social Fetch for X (Twitter)
Pull public X data as JSON: profiles and follower counts, timelines, single posts with engagement metrics, reply threads, follower and following lists, operator search, hashtags, communities, lists, and video transcripts.
X's official API requires a developer account, app approval, and paid tiers before you get meaningful read volume. Social Fetch skips all of that: no developer contract, no OAuth, and no scraper or proxy fleet of your own to keep alive when X changes its front end.
Requests run live on one API key that covers all 25 platforms, with the same response envelope everywhere. You pay per lookup in credits, and meta.creditsCharged shows exactly what each call cost. New accounts get 100 free credits, no credit card required.
How to call the X (Twitter) API
1. Create an API key
Sign up at Social Fetch and copy a key (
sfk_…). New accounts get 100 free credits — enough to check a profile card, pull one tweet, and run a search page against live X data.2. Call a Twitter route
Start with
GET /v1/twitter/profiles/{handle}for identity, then add.../tweets,GET /v1/twitter/tweets,.../replies,.../transcript,search,hashtags, orcommunitiesas the job needs. Sendx-api-keyon every request.3. Read the shared envelope
Branch on
data.lookupStatusbefore writing a row. Logmeta.requestIdfor support. Bill againstmeta.creditsCharged— Twitter lookups and timeline, search, hashtag, and reply-thread pages each run 1 credit, and the field is the source of truth.
What each X (Twitter) route returns
- Profile card by handle — bio, avatar, verification flags, and follower/post metrics from
GET /v1/twitter/profiles/{handle}. - Handle timeline with cursor pagination (
limitup to 100) and optionalincludeReplies/includePinnedtoggles. - Single tweet by permalink or numeric id — text, engagement metrics, media, entities, and quote/reply/retweet flags, with an optional
trimmode for a smaller body. - Reply thread under a status URL, cursor-paged, with
conversationIdandinReplyToStatusIdlinkage. - Video tweet transcripts — a plain spoken-text string, an explicit null when speech isn't detected, and a typed rejection for clips too long to transcribe.
- Operator-first search with
sectiontabs (top/latest/people/photos/videos). Use the advanced search query builder to compile a query. - Hashtag-led discovery with the same section-tab pattern plus
data.peoplerows. - Community metadata (member count, join policy, rules, creator) and paged community post feeds by permalink.
How much does the X (Twitter) API cost?
Twitter routes charge 1 credit per successful request, including GET /v1/twitter/profiles/{handle}, GET /v1/twitter/profiles/{handle}/tweets, GET /v1/twitter/search, GET /v1/twitter/hashtags, and GET /v1/twitter/tweets/replies. Each paginated page is billed separately. Credits never expire on pay-as-you-go packs, and signup includes 100 free credits. Always confirm the actual cost from meta.creditsCharged on the response — this note is a guide, not the source of truth.
Social Fetch vs the official X (Twitter) API
X official API is for posting, account management, and enterprise products under your own developer contract — paid tiers with rate limits. Social Fetch is public-data lookup with a Social Fetch API key, credit-metered per request, same envelope as the rest of the marketplace.
Pull your first X (Twitter) data.
Run a live X (Twitter) request in the playground. 100 free credits, no card, JSON back in seconds.
No credit cardSign up in 30 seconds withGoogleGitHub