Twitter API
Twitter API
Twitter API v1.1 is the discontinued old API (except a few enterprise endpoints) — new projects should use v2.
Existing integrations don't need immediate rewrite
Most v1.1 endpoints discontinued in 2023
Existing projects continue with current tokens. New projects: use v2.
Uptime · 30-day window
About this API
Twitter API v1.1 was launched in 2012 and was the core API of Twitter's ecosystem. A huge developer ecosystem grew around v1.1 (TweetDeck, Tweetbot, various bots, research tools). Twitter launched v2 in 2020-2021 to guide migration. Post-Elon acquisition accelerated v1.1 retirement — February 2023 saw mass v1.1 endpoint discontinuation; remaining enterprise endpoints saw price hikes. If your code still uses v1.1, migrate to v2 ASAP. For new projects, no reason to start with v1.1.
What you can build
- 1Legacy code maintenance until migration
- 2A few enterprise endpoints not yet covered by v2
Strengths & limitations
Strengths
- Existing integrations don't need immediate rewrite
Limitations
- Most v1.1 endpoints discontinued in 2023
- No more feature updates
- Strongly recommend migrating to v2
Example request
curl https://dev.twitter.com/<endpoint>Getting started
Existing projects continue with current tokens. New projects: use v2.
FAQ
How much longer will v1.1 work?+
Remaining enterprise endpoints have no announced EOL date, but Twitter no longer invests in maintenance. Plan migration — don't wait.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST
- SDKs
- python, javascript, go, java
- Response time
- 139 ms
- Last health check
- 5/12/2026, 7:38:32 AM