Determing Twitter API Rate Limit for Statuses / Filter End-point

Viewed 318
2 Answers

You are limited to a single streaming connection connection. Limits in Twitter API are usually with regards to rate limits for requests. But that is for non-streaming requests. If your streaming connection gets dropped, you should look at the error code and respond accordingly.

Here is the Twitter doc with codes and streaming message types. https://developer.twitter.com/en/docs/tweets/filter-realtime/overview/statuses-filter

When your connection does get dropped, you can try to immediately reconnect but not too frequently. It's recommended that you implement a back-off strategy described here. https://developer.twitter.com/en/docs/tweets/filter-realtime/guides/connecting

Also see the section regarding "Stalls."

The statuses/filter endpoint is limited to 1% of the Twitter firehose so if you require more than this amount of data then it may not provide information.

Related