Today, we’re deprecating two features on the Twitter API v1.1 streaming endpoints:
These features will be retired in six months on October 29, 2022.
Additionally, beginning today, new client applications will not be able to gain access to v1.1 statuses/sample and v1.1 statuses/filter. Developers with client apps already using these endpoints will maintain access until the functionality is retired. We are not retiring v1.1 statuses/filter in 6-months, only the ability to retrieve compliance messages. We will retire the full endpoint eventually.
Why we’re deprecating these features
We know that deprecations can be challenging and we want to be transparent about what’s driving this change. Maintaining these v1.1 features requires energy that can best serve our developer community if repurposed towards innovation on the Twitter API v2. We’re committed to making migration to the v2 alternatives (detailed below) easy and to continued investment in the v2 platform.
Begin migrating to v2 replacements
Below are a few resources to help you migrate to the v2 replacements:
Developers using the v1.1 statuses/sample endpoint should adopt the v2 sampled stream endpoint
Quick start guide
Integration guide
Migration information
API reference
Guide: How to use the sampled stream endpoint in Python
Developers using the v1.1 statuses/filter endpoint for compliance purposes, should adopt the v2 batch compliance endpoint
Quick Start Guide
Integration Guide
API Reference
Guide: How to use the batch compliance endpoint in Python with Tweepy
Developers using the v1.1 statuses/filter endpoint, who want to get ahead of an eventual deprecation of v1.1 statuses/filter, should adopt the v2 filtered stream endpoint
Quick start guide
Integration guide
Migration information
API reference
If you have any questions, please reach out to us on the Twitter Community Forums.
3 Likes