In April 2017, we announced the Account Activity API to help developers build solutions that enabled businesses to create better engagement experiences. In December, we announced the enterprise general availability and today we’re excited to announce the Account Activity API is now generally available to all developers through our developer portal.
With this release, we’ve added a for_user_id payload field to all activities. This provides the user ID of the subscriber associated with every activity so developers can better understand why they received an activity and what to do with it. We also added a new unfollow event type which is sent when a subscriber unfollows someone, and we will soon start delivering another new activity type - delete events.
Replacing legacy services
When we announced our plans to retire and replace Site Streams, User Streams, and our REST Direct Message endpoints, we did so as part of our efforts to improve the developer experience and provide a sustainable way to help businesses engage with those looking to connect with them.
We recently published a Tweet thread stating some changes to those plans and can now provide more details about upcoming deprecations. Site Streams, User Streams, and legacy Direct Message endpoints, originally slated for retirement on June 19th 2018, will be deprecated on Wednesday August 16, 2018 which provides 3 months from today’s release of the Account Activity API for migration.
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 be deprecated on August 16th, 2018. Also note that, the Account Activity API allows 15 free subscriptions, a reduction from 35 allowed during the beta. This change will be effective today and will not currently impact any beta users.
Resources for developers
We built a migration guide to assist in the transition from Site Streams and User Streams to the Account Activity API. As a few developers have noticed, there’s no streaming connection capability or home timeline data, which are only used by a small amount of developers (roughly 1% of monthly active apps). As we retire aging APIs, we have no plans to add these capabilities to Account Activity API or create a new streaming service for related use cases. Home timeline information remains accessible for developers via the statuses/home_timeline endpoint.
The Direct Message endpoints on the REST API have been replaced with newer, more functional, endpoints that are generally available. Developers using legacy Direct Message endpoints can refer to our migration guide and begin their migrations now.
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.
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.