Twitter delays the shutdown of legacy notification APIs until August

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. https://t.co/OiZP243Utt

— Twitter Dev (@TwitterDev) May 16, 2018

Twitter has also made a migration guide available to developers as well as a resources page that outlines all of the new changes. "We created a comprehensive resources page to outline these changes to help developers understand the best way to keep solutions up and running, including links to documentation, migration guides and a playbook," Twitter said in a blog post .

Though developers now have three months to switch over to the new API, the new pricing structure might be prohibitively costly for some. A Twitterrific developer tweeted today that the company probably won't be able to afford it. Tapbots, meanwhile, said yesterday that once it was given access to the replacement API it would be able to use it to "replace almost all of the functionality that [Twitter is] deprecating."

It's looking like it won't be financially possible for us to afford the new account activity API from twitter.

— Sean Heber (@BigZaphod) May 16, 2018

关键词:Notification

相关推荐:

Twitter finally details new API, screws third-party apps — again

Twitter Shares Pricing on New Account Activity APIs, Some Third-Party Apps in Jeopardy

Twitter reveals new API that’ll charge third-party clients for old functionality

Twitter delays shutdown of legacy APIs by 3 months as it launches a replacement

Twitter delivers setbacks for third-party apps with new Account Activity API

Twitter moves developer API change to August, third-party app future unclear

Twitter brings new Account APIs for developers and delays plugging off 'ageing' ones to 16 ...

Twitter 推迟关闭旧有 API,向开发者提供替代工具

Here’s what’s really happening to third party Twitter apps on August 16, 2018

Favstar says it will shut down June 19 as a result of Twitter’s API changes for data streams