/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Twitter launches API v2, the first complete rebuild of its API since 2012, in a bid to improve relations with third-party developers

Wooing developers with a new API  —  Twitter is making it easier for businesses, academics, and third-party developers to build on its platform with the launch of its API v2 today.

The Verge James Vincent

Context & Ripple Effects

This launch closes a long arc of estrangement: Twitter spent 2017 trying to repair developer trust with a streamlined platform reset, then monetized access through premium historical-search APIs while delaying legacy shutdowns, before opening Developer Labs betas in 2019 to test the rebuilt endpoints. The v2 release previewed in July adds conversation threading, poll results, and pinned tweets — capabilities the old API never exposed.

First-order effects

  • Third-party developers, businesses, and academics gain modern endpoints for features like threading and polls that were previously inaccessible or required scraping workarounds.
  • Twitter consolidates a patchwork of legacy, premium, and Labs APIs into one supported surface, ending years of fragmented access tiers for existing integrations.

Second-order effects

  • The paid-plan funnel built through Developer Labs and premium search now has a mainstream on-ramp, letting Twitter price v2 access rather than give it away as it did pre-2012.
  • Rival platforms face pressure to match a first-class developer surface, since third-party clients and research tools built on v2 raise switching costs away from Twitter.

Third-order effects

  • If v2 becomes the default and Twitter pushes toward decentralization, the platform's health will depend on external builders — a dependency that cuts both ways whenever ownership or policy changes.
  • The episode reinforces a structural lesson for developers: APIs governed by a single advertising-funded company can be repriced or restricted at any time, favoring multi-platform architectures.

The trend: Social platforms are rebuilding closed, monetized API layers to recapture the third-party ecosystems they froze out earlier in their lifecycles.

Discussion

  • @jack @jack on x
    Build on Twitter again! https://twitter.com/...
  • @twitterdev @twitterdev on x
    It's finally here! 🥁 Say hello to the new #TwitterAPI. We're rebuilding the Twitter API v2 from the ground up to better serve our developer community. And today's launch is only the beginning. https://blog.twitter.com/... https://twitter.com/...
  • @sferik Erik Berlin on x
    I co-authored the open source Ruby library for Twitter (https://t.co/...). It has 4.3k stars on GitHub and has been downloaded 11 million times. I'd love to update the library for Twitter API v2 but I've been denied access to even see the documentation. I guess I won't. 🤷‍♂️ http…
  • @dakami Dan Kaminsky on x
    One problem with the whole API model is nobody specifies how long you can expect an API to still operate. My snap estimate has been twice the average tenure of an employee at the API provider, but there's obvious exceptions once scale gets huge. Any better ideas? https://twitter.…
  • @gedeon Ged Maheux on x
    I talked to the @verge about the new Twitter API rollout announced today and what it may mean for @Twitterrific - https://www.theverge.com/... https://twitter.com/...
  • @androiddev @androiddev on x
    📣 Introducing in-app review API! 📣 Developers can now ask for ratings and reviews from within your app with the new in-app review API. See how → https://android-developers.googleblog.c om/ ... #11WeeksOfAndroid https://twitter.com/...
  • @twitterapi @twitterapi on x
    Twitter API v2: Early Access released Today we announced Early Access to the first endpoints of the new Twitter API! #TwitterAPI #EarlyAccess #VersionBump https://twitter.com/...
  • @kayvz Kayvon Beykpour on x
    Today marks the beginning of a new phase of our developer API. Really excited to see what the dev community builds with the #TwitterAPI. Also, the roadmap is public so please share your feedback and suggestions! https://trello.com/... https://twitter.com/...
  • @obra Jesse Vincent on x
    Fool me once, shame on you. Fool me twice, it's time to switch to federated social media. https://www.theverge.com/...
  • @kfury Kevin Fox on x
    I'm curious to know what Twitter client developers think. https://twitter.com/...
  • @evan_van_ness Evan Van Ness on x
    Given that Twitter often suspends people despite no ToS violations (it's happened to me ~7x) AND the fact that Twitter already screwed devs once, why should anyone trust you? (Eth fixes this) https://twitter.com/...
  • @kurrik Arne Roomann-Kurrik on x
    Erik has probably contributed more value to Twitter's developer ecosystem than any Twitter employee. Twitter always knew how to build a platform but never figured out how to run one https://twitter.com/...
  • @dfreelon Deen Freelon on x
    Ooh, major changes to @TwitterAPI—including a new academic product track! 🤩🤩🤩 https://blog.twitter.com/...
  • @tessak22 Tessa Kriesel on x
    Soooooooo excited to be a part of this next adventure with #TwitterDevs as they dive into the new #TwitterAPI! Unfortunately, I'm not as hands-on today as I'm packing my @uhaul to move to Colorado! 💙 Excited to hear your thoughts, my DMs are open and I'll be back on Tuesday! http…
  • @helvetiica @helvetiica on x
    It looks like poll results, conversation threads, Tweet annotations, metric data, etc. are now available for third-party Twitter clients! 🎉 https://twittercommunity.com/ ... https://twitter.com/...
  • @anthony Anthony DeRosa on x
    Twitter's API refresh has been delayed because of the July 15th security breach https://blog.twitter.com/...
  • @evanmcmurry Evan McMurry on x
    Can we get Crowdtangle back? https://www.theverge.com/...
  • @tomwarren Tom Warren on x
    Twitter stabbed developers in the back years ago and now it wants them back. Good luck with that 🍳 https://twitter.com/...
  • @backlon Dieter Bohn on x
    Ah, it would be a super rational move for developers to invest a huge amount of their time and resources building businesses on top of an API from the historicially consistent company called Twitter, known throughout the world for stable predictable treatment of 3rd-party develo …