Limitations of the Streaming API?

Question

I understand that the Twitter REST API has strict limits on the request (several hundred times in 15 minutes), and that the streaming API is sometimes better at retrieving data in real time.

My question is, what exactly are the limitations of the streaming API? Twitter refers to a percentage of its documents, but not a specific amount. Any insight is greatly appreciated.

What am I trying to do:

• A simple page for viewing the last tweet (and the date / time of its publication) from ~ 1000 Twitter users. It seems like I would quickly hit the limit using the REST API, just like for the streaming API?

Answer 1

You should be fine using the Streaming API unless these ~ 1000 users tweet more (very) approximately 60 tweets per second at any time.

Using the statuses/filter streaming API endpoint with the follow parameter, you can use up to 5000 users. There is a speed limit, unless the stream returns more than 1% of all tweets that are currently being tweeted. (60 tweets per second make up 1% of the average tweet rate, which always fluctuates, so don't rely on this number.)

If your flow exceeds 1% of the threshold, you may find this. (Pay attention to LIMIT .) Then you should use the REST API to search for missing tweets.

Answer 2

Twitter simply will not allow multiple streams from a single registered application / account. This will close the older one.

Also, too many connection attempts are not allowed and will block the user.

Reference Documents: Public Streaming API