Twitter delays shutdown of legacy APIs to August 16, makes Account Activity API generally available, reduces free Premium Sandbox subscriptions allowed to 15
again Gary Ng / iPhone in Canada Blog : Twitterrific: New Twitter API Cost of $2899/Month Not Financially Viable Mallory Locklear / Engadget : Twitter delays the shutdown of legacy notification APIs until August Jesse Hollington / iLounge : Twitter extends API shutdown deadline to August, third-party apps may still lose functionality Twitter : Enabling all developers to build on the Account Activity API Zac Hall / 9to5Mac : Twitter moves developer API change to August, third-party app future unclear Tweets: Jon Henshaw / @henshaw : Twitter became what it is thanks to 3rd party developers making apps with their API. Once they got to a place of market dominance, they crapped all over them with changes to their API. Now the developers that stuck it out are being fooled twice. http://daringfireball.net/... Mike / @sirstendec : Whenever I get annoyed at how lackluster Twitch's new API helix is, and how it's missing tons of things, and how they still seem keen on removing the good API at the end of the year with no time for third parties to adapt, remind me at least they're not Twitter. http://twitter.com/... Robert McNees / @mcnees : Reducing the functionality of 3rd party @Twitter clients seems like a bad move, imo. If you make those clients less useful, the segment of users that really depend on them will, by extension, find Twitter less useful. http://twitter.com/... Joaquim Vergs / @joenrv : Pretty sad about this announcement, not at all what I hoped for. They basically designed their API to make customer service chatbots, while making sure you can't use it for a normal client app use case... rip my dreams of full account activity in Falcon http://twitter.com/... Twitter Dev / @twitterdev : Today we're excited to announce the general availability of Account Activity API. Now developers can get started for free, upgrade to premium as they scale, and move to enterprise when they need even more subscriptions or enterprise functionality. https://developer.twitter.com/ ... Twitter Dev / @twitterdev : We're also making a change to our deprecation date for Site Streams, User Streams and legacy Direct Message endpoints. Those services, originally slated for retirement on June 19th, will be available until August 16th, 2018. http://blog.twitter.com/... Tom Warren / @tomwarren : Twitter screws the developers that helped build and shape Twitter once again http://twitter.com/...
Context & Ripple Effects
This May 2018 announcement is the opening move in Twitter's long squeeze on its developer ecosystem: the company gives third-party clients like Tweetbot and Twitterrific a three-month reprieve by delaying the retirement of Site Streams, User Streams, and legacy DM endpoints to August 16, while making the Account Activity API generally available with a free starter tier and premium/enterprise upgrades above it.
Read against the later coverage, the structure is clear — the same endpoints were ultimately killed outright when Twitter announced it was ending legacy API support, and the paid-tier logic introduced here hardened into discontinuing free API access entirely. What looked like a deadline extension was the start of a migration funnel toward paid plans.
First-order effects
- Developers of notification-dependent clients get until August 16 to rebuild on the Account Activity API or lose core functionality, while the cut to 15 free Premium Sandbox subscriptions forces teams already testing premium endpoints to ration accounts or pay.
Second-order effects
- Client makers such as Iconfactory (Twitterrific) and Tapbots (Tweetbot) confront per-account enterprise pricing that makes consumer-priced apps economically unviable — the coverage cites Twitterrific's developers calling a $2,899/month tier not financially viable.
- Users of third-party clients become the bargaining chip: their apps' survival now depends on whether their developers can absorb or pass along API costs, shifting loyalty pressure back toward Twitter's own clients.
Third-order effects
- If the pattern holds, open API access converts into a metered product line — which is exactly what followed: rebuilt APIs offered as a paid beta via Developer Labs, then a developer agreement updated with a clause banning third-party clients outright, leaving apps broken with no recourse.
- The structural lesson for every platform with an API ecosystem is that free developer access is revocable infrastructure, and businesses built on it inherit single-vendor risk they cannot contract away.
The trend: Platform companies are progressively converting open developer APIs into paid, restricted access tiers until independent clients are either priced out or banned — with Twitter running the arc from deadline extensions to an outright client ban over five years.