"Twitter API," "X API," and "Twitter scraper" get used for the same shopping trip, but they usually mean three different products: write access and elevated tiers under X's contracts, public enrichment without an X developer app, or bulk scrapes that ignore first-party packaging.

Mixing those up is how you end up paying enterprise rates for a follower count, or wiring a marketplace Actor when you needed posting scopes. For the official meter vs public-data credit math, see Twitter / X API pricing.

This is a pricing and coverage comparison for June 2026. Re-check each vendor's site before you commit budget.

Social Fetch is my pick for sync REST over public X profiles, tweets, replies, search, hashtags, communities, and tweet transcripts, especially if you already normalize creators across TikTok and Instagram. Prefer the official X API when you need posting, DMs, OAuth-on-behalf-of, or a first-party compliance path. Prefer Apify when you need a custom Actor or a scheduled batch dump. Prefer EnsembleData or SociaVault when you want another sync social API and X is one of a few platforms you care about.

The short list

1. Social Fetch — sync REST for public X data, same envelope as other platforms
2. X API (official) — first-party route for write access, elevated products, and X-signed contracts
3. Apify Twitter/X Actors — marketplace scrapers when you need custom fields or scheduled runs
4. EnsembleData — sync social API with monthly unit plans that include X
5. SociaVault — pay-as-you-go social API with X in the mix
6. RapidAPI Twitter listings — discovery marketplace, not one production contract

Full X route list and examples: Twitter / X platform page. Cost fork: Twitter / X API pricing.

How I rank Twitter/X data APIs

I rank on production behavior:

1. What you can actually call — profiles, tweets, replies, user timelines, keyword search, hashtags, communities, transcripts. Count real paths, not "Twitter support" on a marketing grid.
2. Official vs public enrichment — write scopes and elevated access belong on X's API. Public cards and keyword alerts often do not need an X developer app.
3. Quota vs credits — X sells tiered access that changes packaging often. Credit APIs trade that for prepaid lookups; know which meter you are buying.
4. Sync vs async — one HTTP response you can await in a product request, or start-a-run / poll-a-dataset.
5. Error shape — typed outcomes and a requestId beat silent empty HTML when a handle is protected or search returns nothing.
6. Multi-platform tax — if your app already pulls TikTok and Instagram, does X force a second schema and a second vendor?
7. Compliance fit — official API when your contract with X requires it; third-party public-data APIs for enrichment. Read X's Terms for your use case. I am not your lawyer.

Twitter / X pricing compared

Every figure below is indicative for June 2026. Re-check before you buy.

Sticker price is not the whole decision. Credit expiry, daily unit resets, and whether failed infrastructure errors bill change real cost more than a few cents per thousand on a pricing table.

For Social Fetch's billing rules (including private / not-found outcomes that still complete a lookup), see Credits.

Ranked picks

1. Social Fetch — public X over one REST key

Best for: product teams and agents that need public profile cards, tweets, replies, search, communities, and tweet transcripts without an X developer app, and that already (or soon will) pull other social platforms.

Social Fetch exposes first-party X routes under /v1/twitter/*: profile by handle, profile tweets, tweet detail, replies, tweet transcript, keyword search, hashtag search, community detail, and community tweets. Responses use the shared { data, meta } envelope. Follower counts land in the same metrics conventions as other platforms, so cross-network creator scores do not fork on field names.

Sync GET routes cover the common path without Actor run polling. Search sits next to profile and tweet detail (see Twitter search API for filters and pagination). Every response carries meta.requestId and meta.creditsCharged. One API key covers TikTok, Instagram, YouTube, and the rest of the catalog. Signup includes 100 free credits with no card; PAYG packs do not expire.

Limits to know: this is public enrichment, not X's posting API, DMs, or elevated analytics products. Search and heavier routes can cost more than a simple profile GET; trust meta.creditsCharged and the operation docs. Empty search results still complete a lookup and can bill; lookup_failed and 503 temporarily_unavailable do not. Model that before you poll hourly. Protected accounts are not returned as fake public data; expect typed lookup outcomes, not invented timelines.

Pricing: free (100 credits) → Starter $14 (1,000) → higher packs on pricing. Credits charge on completed lookups. See Credits for the full policy.

Default pick when X is one surface in a multi-platform product, or when you want keyword search and profile cards without negotiating an X enterprise seat.

See the X (Twitter) hub for the full route list.

2. X API (official) — first-party when you need first-party

Best for: apps that post or reply as users, need OAuth scopes, DMs, elevated access, or must stay inside X's own access model and contracts.

The official X API is the correct product for write paths and anything procurement insists must come from X. Tiers, rate limits, and product packaging change often enough that teams treat access as a procurement problem, not an engineering one. That works when ownership and compliance require it. It is expensive friction when you only need a public profile card or a keyword alert cron.

First-party ToS path. Write access and OAuth-on-behalf-of. Good for products that already run on X developer apps and need posting or elevated products third parties cannot honestly sell.

Pricing and tier names move. Free and low tiers surprise people who treat "API access" as unlimited search for a monitoring cron. Commercial scrapers that ignore the official API are a different risk category than calling X's endpoints with a project key.

Pricing: free and paid X developer tiers; packaging changes. Read current X developer pricing before you promise volume, or start with our walkthrough: Twitter / X API pricing. This is not prepaid social credits that charge only on completed public lookups.

Use it when write scopes, OAuth-on-behalf-of, or an X-signed contract are requirements. Supplement or replace it for public enrichment and multi-platform apps if the tier math fails your product.

3. Apify — Twitter/X Actors for custom and batch work

Best for: scheduled handle dumps, niche field extraction, and scrapers you want to configure as Actors rather than maintain as a fleet of browsers.

Apify hosts many Twitter/X Actors (profiles, tweets, search, followers lists depending on the Actor). You start a run, poll, download a dataset. Schemas differ by Actor author. Billing mixes platform subscription, compute, and per-event fees; monthly plan credits expire. Per-result costs vary widely by Actor. Model the specific Actor's pricing, not a generic "Apify is cheap" assumption.

Marketplace breadth helps when no managed REST route exposes the field you need. Scheduling and dataset export are built into the platform.

You are buying a runtime, not one X schema. Actor quality varies. Sync product UIs that need a single HTTP round trip fit poorly. X anti-bot pressure hits Actor authors unevenly.

Pricing: free (~$5/mo platform credit) → Starter and higher monthly plans. See Social Fetch vs Apify.

Right for batch and custom scrapes. Wrong as your only integration if you want one typed client for profile + search in a request handler.

4. EnsembleData — sync social with daily unit resets

Best for: teams that want sync GET social JSON (including X) and are fine with monthly plans that reset units daily.

EnsembleData sits in the same lane as Social Fetch: synchronous requests, JSON responses, one token. Coverage includes X among other social networks. The purchase model is monthly plans with a daily unit allowance that resets at 00:00 UTC. That differs from prepaid packs that never expire and charge only on completed lookups.

Real sync REST competitor. Failed internal errors are not billed (similar honesty bar to our lookup_failed / 503 policy). Straightforward for steady daily volume that fits the unit cap.

Spiky workloads hate daily resets. A launch-day burst can burn the day early and stall until UTC midnight. Platform breadth is narrower than Social Fetch's catalog. Compare your mix before the logo wins: Social Fetch vs EnsembleData.

Reasonable if X is one of a few networks and monthly unit math fits. Prefer prepaid credits if your traffic is bursty.

5. SociaVault — simple PAYG for a smaller social set

Best for: pay-as-you-go social lookups when you want another first-party REST option and X is in scope.

SociaVault overlaps Social Fetch on several networks, including Twitter/X. Credits are prepaid and do not expire. Docs publish complexity multipliers on some routes (comments, demographics), so profile-only math can understate a comments-heavy product. Entry packs are commonly cited around $29 for 6,000 credits. Confirm live on sociavault.com before you budget.

Same product category. Self-serve. No Actor polling for the common path. PAYG shape that does not force a monthly seat.

Verify credit weights for the routes you will actually call. Tooling and envelope differ. Catalog is smaller than Social Fetch's matrix. Side-by-side: Social Fetch vs SociaVault.

Fine shortlist peer. Pick on price-at-your-mix, docs, and whether you need the wider Social Fetch surface.

6. RapidAPI Twitter listings — browse, then graduate

Best for: finding a niche X endpoint over a weekend without signing an enterprise contract or committing to one vendor's schema.

RapidAPI is a marketplace of third-party Twitter/X scrapers, not one production contract. Billing and discovery sit on the platform; the actual API comes from an independent publisher. Search the catalog and you will find several "Twitter API" listings with different JSON shapes, rate caps, and maintenance habits. The test console makes weekend prototypes easy.

That speed stops helping once X is load-bearing. Multi-platform products usually need a second listing for Instagram and a third for YouTube, each with its own key, schema, and support path. When a publisher changes fields or abandons a listing after an X UI change, tickets often bounce through RapidAPI to someone you never onboarded. Typical marketplace social scrapers land around $2.50–$4+ per 1,000 requests depending on the listing; confirm the publisher's meter before you budget.

Fast discovery across many scrapers. Cheap Basic tiers for throwaway experiments. Works if you already centralize unrelated APIs on one RapidAPI invoice.

No shared envelope. Publisher churn. Per-minute caps on popular Pro tiers that throttle live product traffic. Fragmentation tax when X is only one of several networks.

Keep it for exploration and hackathons. Graduate to a first-party sync API when profile + search sit in a request handler, or when you need the same parser as TikTok and Instagram. Longer take: Social Fetch vs RapidAPI.

Profile lookup is often enough

A lot of "we need the Twitter API" tickets are really "confirm this handle exists and pull follower count." That job does not require write scopes, search pagination, or an Actor.

For a one-off paste-and-read check in the browser, use the free tool instead of wiring keys:

• Free Twitter / X profile viewer — handle or x.com / twitter.com URL → bio, followers, verification signals
• Same production path as GET /v1/twitter/profiles/{handle} behind Turnstile and fair-use caps (1/min · 3/hour · 10/day per IP)
• Tweet lists, replies, and search stay on the paid API

Protected accounts may return limited fields. The free tool is for spot checks, not screening a spreadsheet. When you need volume, move to an API key and the X platform routes.

Which API fits which job

• Multi-platform creator product, sync JSON → Social Fetch (X hub)
• Posting / OAuth / elevated X products → Official X API
• Nightly handle scrape with custom fields → Apify Actor
• Sync social with daily unit caps → EnsembleData
• Simple PAYG peer on a smaller catalog → SociaVault
• One-off public profile in the browser → /tools/twitter-profile-viewer
• Keyword alerts without an X developer app → Social Fetch search (guide)

If you only need X today but Instagram next quarter, pick the option whose envelope you can reuse. Rewriting parsers per platform is where most "cheap" APIs get expensive.

Questions before you buy

1. Do you need write scopes, or public enrichment? That fork decides official X vs third-party first.
2. Will search volume fit your tier or credit budget? Model polls × credits (or X rate limits) before you promise real-time alerts in a UI.
3. Is profile card enough? If yes, try /tools/twitter-profile-viewer before you design around search.
4. Sync or batch? Product request handlers prefer sync. Overnight dumps can live on Actors.
5. One schema across platforms? Call X and TikTok with the same parser. If you need if (platform === "twitter"), you do not have unification.
6. Do credits or units expire / reset? Spiky workloads hate monthly or daily resets.
7. Can you preview without shipping? Use a playground, free credits, or the free profile viewer before you lock a vendor.

Frequently asked questions

What is the best Twitter/X Data API in 2026?

For public sync REST with profiles, tweets, replies, search, communities, and transcripts, and the same envelope as other social platforms, Social Fetch is my pick. I built it. The official X API wins for write access and first-party contracts. Apify wins for custom Actors. EnsembleData and SociaVault are real sync peers with different billing shapes.

Is the official X API free?

X publishes free and paid tiers; packaging changes. Treat free access as a small allowance with rate limits, not unlimited production search. Read current X developer pricing before you promise volume.

Do I need an X developer account for Social Fetch?

No. You need a Social Fetch API key. Details and route list: /platforms/twitter.

Twitter scraper API vs X API — which should I use?

Use the official API when you need X's auth model, posting, or elevated products. Use a managed public-data API when you need enrichment without an X developer app, or when tier math and multi-platform schemas fail your product. Scrapers and Actors fill gaps neither covers; they also shift maintenance and compliance risk onto you.

Can I look up an X profile without an API key?

Yes, for spot checks: /tools/twitter-profile-viewer. Rate-limited. For product volume, use GET /v1/twitter/profiles/{handle} with a key.

When does Social Fetch charge credits on X routes?

On completed lookup attempts, as documented per endpoint. That includes 200 responses where data.lookupStatus is private or not_found, and empty search pages that still resolved. lookup_failed and 503 temporarily_unavailable are not charged on metered lookup routes. Always read meta.creditsCharged. Full policy: Credits.

Smoke-test a profile or search in the playground, or start with 100 free credits on pricing. For one public handle without an API key, open the free Twitter / X profile viewer. Official vs public-data cost models: Twitter / X API pricing.