The Twitter API is Finished. Now What?
Twitter's API has spawned over 50,000 applications that connect to it, taking the promise of fertile APIs we first saw with Flickr half a decade ago and bringing it to new heights. Now, the first meaningful efforts to support Twitter's API …
Context & Ripple Effects
Anil Dash frames a turning point for what he calls the most fertile developer API since Flickr opened up half a decade earlier: more than 50,000 applications now connect to Twitter, and the company is signaling that the anything-goes phase is over. The tell is the Contributors feature Twitter unveiled two days before this piece, which formally separates select — largely corporate — accounts from ordinary users, marking the start of a courtship of big business.
The backdrop matters: commentary like VentureBeat's October 2008 obituary for Twitter treated fragility as the story, yet the platform kept compounding — real-time search moments like the Hudson River landing photos, conference back-chat, even emergent microsyntax conventions built atop the API. Dash's point is not that Twitter dies, but that its openness becomes a managed resource, with support flowing first to partners who matter commercially.
First-order effects
- The developers behind the 50,000-plus connected applications face a shift from an open interface to one where Twitter's meaningful engineering effort goes to vetted partners — plain API parity is no longer the default promise.
- Businesses using Twitter get a formal identity layer: Contributor status distinguishes brand accounts from regular users, giving companies an official channel the general developer base does not receive.
Second-order effects
- Third-party client makers must compete on features and polish rather than raw access, because Twitter now allocates API attention by commercial value rather than by who asks first.
- Enterprise social-media tooling consolidates around officially blessed integrations, squeezing out hobbyist middleware that once differentiated itself purely on API availability.
Third-order effects
- If the pattern holds across consumer platforms, the fertile-API era Dash traces to Flickr gives way to a tiered-access model in which the platform, not the ecosystem, decides which builders get supported — a structural precedent for every network service that follows.
- Developer ecosystems become a lever of platform strategy rather than a commons, pushing independent builders toward either partnership or migration to more open alternatives.
The trend: Consumer web platforms are moving from open, unmanaged developer APIs toward curated, commercially aligned access tiers, with Twitter as the template case.