Twitter makes its v2 API, announced in August 2020, the default for developers, giving third-party apps more freedom as it aims to become more decentralized
Twitter's new API is finally official, which could mean good things for third-party clients — Twitter has announced … Source: Twitter .
The change matters because Twitter is explicitly pairing broader third-party-app capabilities with a decentralization goal, rather than treating the API solely as a legacy integration layer.
First-order effects
Third-party Twitter clients and other developers gain the v2 API as their default integration path, with the added freedom Twitter says the new interface provides.
Twitter shifts developer onboarding and ongoing integrations toward the rebuilt platform, reducing reliance on its older API estate.
Second-order effects
Developers that stayed on legacy interfaces face a clearer incentive to migrate, following Twitter's earlier delays to legacy-API shutdowns and its reduced free sandbox access.
Twitter's ability to define which features are exposed through v2 becomes a more consequential lever over the kinds of third-party clients that can compete for users.
Third-order effects
API access becomes a central governance mechanism for Twitter's decentralization strategy: open capabilities can broaden the client ecosystem, while later restrictions can narrow it quickly.
The subsequent ban on third-party clients shows that developer investment in a platform API is structurally exposed to policy reversals, even after a period of expanded access.
The trend: Social platforms are treating APIs less as neutral developer infrastructure and more as strategic controls over client competition, ecosystem openness, and platform direction.
Introducing a new era for the Twitter Developer Platform! 📣The Twitter API v2 is now the primary API and full of new features ⏱Immediate access for most use cases, or apply to get more access for free 📖Removed certain restrictions in the Policy https://blog.twitter.com/... https:…
If Twitter actually makes good on these API promises, it would be a massive rollback of its terrible policies limiting 3rd party apps from so long ago. I want to believe... But I also see it used the phrase “doubling down” so. https://www.theverge.com/...
Twitter is hoping developers will forget the days when it shut off apps without notice, and generally behaved towards its ecosystem like “a drunk guy with an Uzi,” as @cdixon memorably put it at the time https://www.theverge.com/... via @Verge
Twitter finally opening up the API and maybe decentralized. For those here for 10 years you will understand the joke “I should restart seesmic”! (Twitter basically one day told me I couldn't do what I was doing anymore and changed all the rules) https://www.theverge.com/...
Don't let their marketing sweet talk you in, @TwitterAPI remains hostile to developers unless you're a massive company, and none of this will last. https://twitter.com/...
Twitter's API updates are exciting. Making it easier to get started, relaxing some rules, adding new endpoints and increasing some of the limits. A massive win for everyone, devs and Twitter users. https://blog.twitter.com/...
Since the new API has basically the same rate limits as the old one for the “free” tier, I don't see how this is really going to help. The real problem has always been the limits on search and the low number of API calls an app can make w/o paying a lot of money. https://twitter.…
Twitter API v2: easier and faster signup (in seconds!), opening our developer policy (especially for 3rd party clients), and entirely new endpoints and features! Please give us feedback so we can continue to open and evolve it... https://twitter.com/...
Twitter, which either acquired or neutralized most third-party Twitter apps, is now back heroically letting people create third-party Twitter apps. https://twitter.com/...
It's sincerely amazing (and good!) that we have looped all the way back around to “it's ok to build third-party Twitter clients again.” https://twitter.com/...