
The deprecation, the gates, the third-party seam.
Section: developer reference
Twitter API v2 is the current generation of the official X developer platform. It replaces v1.1, which X Corp has deprecated on a rolling schedule. Most new official documentation, code samples, and SDKs target v2 exclusively.
What follows: what the version bump changed, what it broke, and where the third-party seam offers a different model entirely.
The changes ledger
Where the third-party seam fits
- You need first-party SLA guarantees on the wire.
- Your use case requires official write actions ($0.015 per post created).
- Compliance or procurement requires a direct vendor relationship with X Corp.
- You already have an Enterprise contract — no incremental third-party benefit.
- Price-sensitive workloads. Per-call cents instead of $0.005 per post read ($5,000 per million posts).
- No X developer account or payment card on file; you need the key in five minutes.
- One key serving many small use cases — narrower surface to manage.
- Fast iteration and prototyping over canonical guarantees.
Migration in four strokes
Swap base URL
From api.twitter.com/2/ to api.twitterapi.io/twitter/. The path under the base is different per endpoint; the docs.twitterapi.io reference lists every one.
Swap auth header
v2 carried the credential as Authorization: Bearer <token>. TwitterAPI.io carries it as X-API-Key: <key>. The key sits in /dashboard, available the moment Google sign-in completes.
Adapt response unpacking
v2 returns data: [...] with a sibling includes: {...} block that the caller stitches back together by id. TwitterAPI.io flattens this — each tweet object carries its embedded author profile inline. Remove the includes-join code.
Keep the query syntax
Operator vocabulary (from:, since:, until:, filter:, lang:, near:) is unchanged. Anything that worked in v2 search strings still works.
Notes
Is Twitter API v1.1 still available?
Most v1.1 endpoints are deprecated by X Corp. Some still respond but with deprecation warnings; many have been removed entirely. New projects should not target v1.1.
Is the official v2 API free?
No. Official v2 access is pay-per-use with no subscriptions: $0.005 per post read, $0.010 per user read, $0.015 per post created ($0.200 if it contains a URL). Saving a first eligible card gives $20 of free credits, plus a match of the first auto-recharge up to $50. Pay-per-use is capped at 3 million post reads per monthly billing cycle; above that, Enterprise via an interest form with no public price. You need an X developer account and a saved payment card.
Is TwitterAPI.io a v2-compatible API?
TwitterAPI.io is an independent third-party API with its own surface — it is not a drop-in v2 client. Functionally it covers the same use cases (search tweets, fetch users, follower graphs, real-time stream) with a different request/response shape. Migration from an existing v2 script is usually thirty minutes: swap base URL, swap auth header, lightly adapt response unpacking.
Which version should new projects use?
If your budget supports it and your use case fits official pay-per-use pricing, use official v2 — first-party guarantees, canonical documentation. If you're outside that bracket (price-sensitive, fast iteration, no X developer account or payment card on file), a third-party API like TwitterAPI.io is the standard answer.
Continue
Issue a key on TwitterAPI.io. Make the migration in one sitting.
Begin →