search

ttezel / twit

Twitter API Client for node (REST & Streaming API)
4.32k stars 573 forks source link

Bad Twitter streaming request: 403, "Please use V2 filtered and sample volume stream as alternatives" #571

Open Hodari-hub opened 2 years ago

Hodari-hub commented 2 years ago

I'm trying to access twitter's API v1.1 filtered streaming endpoint with my new developer account, but it gives me a 403 error. Also, it gives me the Twitter replay message that says, "Please use V2 filtered and sample volume stream as alternatives". It seems like the Twitter streams endpoint has been deprecated. How do we solve this issue?

maziyarpanahi commented 2 years ago

You need to use the v2 APIs: https://twittercommunity.com/t/deprecation-announcement-removing-compliance-messages-from-statuses-filter-and-retiring-statuses-sample-from-the-twitter-api-v1-1/170500

The 1.1 still works (I have many of them) and the warning is just a warning to let you know. I highly recommend to not even bother finding out what's wrong here, try to start using V2 APIs and not waste time on something that won't exist in a short amount of time.

VoidGekido commented 2 years ago

You need to use the v2 APIs: https://twittercommunity.com/t/deprecation-announcement-removing-compliance-messages-from-statuses-filter-and-retiring-statuses-sample-from-the-twitter-api-v1-1/170500

The 1.1 still works (I have many of them) and the warning is just a warning to let you know. I highly recommend to not even bother finding out what's wrong here, try to start using V2 APIs and not waste time on something that won't exist in a short amount of time.

but how would we switch to v2 APIs what needs to be done?

revathiest commented 1 year ago

You need to use the v2 APIs: https://twittercommunity.com/t/deprecation-announcement-removing-compliance-messages-from-statuses-filter-and-retiring-statuses-sample-from-the-twitter-api-v1-1/170500

The 1.1 still works (I have many of them) and the warning is just a warning to let you know. I highly recommend to not even bother finding out what's wrong here, try to start using V2 APIs and not waste time on something that won't exist in a short amount of time.

The 1.1 works for applications created before April 29th. New applications since then receive the error and cannot connect.

jerrychong25 commented 1 year ago

You need to use the v2 APIs: https://twittercommunity.com/t/deprecation-announcement-removing-compliance-messages-from-statuses-filter-and-retiring-statuses-sample-from-the-twitter-api-v1-1/170500 The 1.1 still works (I have many of them) and the warning is just a warning to let you know. I highly recommend to not even bother finding out what's wrong here, try to start using V2 APIs and not waste time on something that won't exist in a short amount of time.

but how would we switch to v2 APIs what needs to be done?

Hi @VoidGekido and @maziyarpanahi ,

Mind to share detailed steps on how to migrate from V1 to V2?

Thank you in advance!