Twitter API: REST and Streaming, what's the difference?

Question

Can someone summarize the differences between the Twitter REST API and its streaming API?

And does any of them use Push technology?

Answer 1

The REST API allows you to request or change a user account. You do not need their permission to request your account, you need to change your account. They provide permission through OAuth authentication.

The streaming API provides tweets based on search terms or for specific users that you request, as well as author information in real time. You do not need permission from the author of the tweets. To use streaming, you must be logged into your Twitter account using either basic or OAuth authentication.

None of them use push, but streaming is a continuous network connection, so it is real-time delivery, which makes it functionally similar to push.

Answer 2

For everyone who came to this recently, the REST API (v1.0) is now retired , with v1.1 being the only version. This one now requires authentication for everything, including reading.

Authentication Required for All Endpoints

In version 1.1, we need applications to authenticate all their requests with OAuth authentication 1.0a or only for applications. Not only will this visibility help us prevent offensive behavior, but it will also help us understand how application categories use the API. We will apply this understanding to better the needs of developers as we continue to develop the platform. At this time, all authentication requires a user context, but in the coming weeks we will insist on supporting an authentication form, not requiring a user context.

Answer 3

In fact, you can use the search through the REST API. For example, this is the only way to combine the geo AND keyword, while the Stream API can only use OR logic.

I think this is about defacto streaming, as Adam Green said.