Comparing Twitter API’s sample stream endpoints
The v2 sampled stream endpoint is replacing the v1.1 statuses/sample endpoint. If you have some code, apps, or tools that use an older version of the sample stream endpoint, and are considering migrating to the newer Twitter API v2 endpoint, then this set of guides is for you.
The following tables compare the various types of sampled stream endpoints:
Description | Standard v1.1 | Twitter API v2 |
Host domain | https://stream.twitter.com | https://api.twitter.com |
Endpoint path | 1.1/statuses/sample.json | /2/tweets/sample/stream |
Authentication | OAuth 1.0a User Context | OAuth 2.0 App-Only |
HTTP methods supported | GET | GET |
Default request rate limits | 8 connection requests per minute | 50 connection requests per 15 min |
Maximum allowed connections | 2 | 1 |
Recovery and redundancy features | None | Essential and Elevated access levels: Academic research access level: |
New JSON format | Standard v1.1 format | Twitter API v2 format (determined by fields and expansions request parameters, not backward-compatible with v1.1 formats) To learn more about how to migrate from the Standard v1.1 format to the Twitter API v2 format, please visit our data formats migration guide. |
Supports selecting which fields return in the payload | No, data format pre-determined | ✔ |
Supports specifying the language of Tweets returned | ✔ | |
Supports the annotations field | ✔ | |
Supports requesting specific metrics | ✔ | |
Supports the conversation_id field | ✔ | |
Provides Tweet edit history |
✔ | ✔ |
Requires the use of credentials from a developer App associated with a Project | ✔ |