Twitter | Search | |
Twitter Dev
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.
Reply Retweet Like More
Twitter Dev May 16
Replying to @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.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
Site Streams and User Streams are being replaced by the Account Activity API which is now available in our developer portal. Developers without access can apply for an account to begin their migration. Please refer to our migration guide.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
There’s no streaming connection capability as is used by only 1% of monthly active apps. Also there's no home timeline data. We have no plans to add that data to Account Activity API or create a new streaming service. However, home timeline data remains accessible via REST API.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
Now that a version of the Account Activity API that delivers a full set of activities is generally available, the beta that delivered only Direct Messages will also be deprecated on August 16th, 2018.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
We are also changing the number of subscriptions available for free to 15, down from the 35 that was available during the beta. This change will be effective today.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
The Direct Message endpoints on the REST API have been replaced with newer, more functional endpoints and developers can migrate now. The legacy endpoints will be deprecated at the same time as User Streams and Site Streams on August 16th, 2018.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
We have resources that detail the changes that are being made. These resources describe the best way to keep your solutions up and running, including links to documentation, migration guides, a playbook, and a video series.
Reply Retweet Like
Twitter Dev May 16
Replying to @TwitterDev
If you have additional questions on our APIs or would like some help as you make changes, our team and expert community are available to help in our developer community forums.
Reply Retweet Like
Liberty May 16
Replying to @TwitterDev
Please reconsider the streaming. 1% might seem small until you consider power laws and how they’re probably your biggest power-users. Don’t break third party apps.
Reply Retweet Like
Reinhardt May 16
is screwing over users and developers with this. , , , , and are all affected by this. Fucking over devs is not the way to go.
Reply Retweet Like
Matthew Fern May 16
Replying to @TwitterDev
Looks like is trying to kill off third-party clients again, by replacing the APIs they all use and making the (inferior) replacements essentially unaffordable to use at scale.
Reply Retweet Like
Chris Anderson May 16
Replying to @TwitterDev @jack
Don’t do this. This will kill Twitter Mac clients that many users rely on when lacking a native Mac Twitter application.
Reply Retweet Like
Mike uǝɥoƆ May 16
Replying to @TwitterDev
I hope twitter goes out of business when you keep screwing over developers and alienating your most active users. You’ll have to pry Tweetbot and Twitterrific out of my cold dead hands. I will never use Twitter app.
Reply Retweet Like
Matt May 16
Replying to @TwitterDev
this is a bad plan. a terrible plan. great plan to drive away the people who make twitter great.
Reply Retweet Like
Alex May 16
Replying to @TwitterDev
lol you jerk
Reply Retweet Like
Patrick Thornton May 16
Replying to @TwitterDev
I don't get why you have so much disdain for your most active and loyal users.
Reply Retweet Like
Nate #SaveTheExpanse May 16
Replying to @TwitterDev @jack
Reply Retweet Like