Standard v1.1 compared to Twitter API v2
If you have been working with the standard v1.1 GET statuses/show and GET statuses/lookup, the goal of this guide is to help you understand the similarities and differences between the standard and Twitter API v2 Tweet lookup endpoints.
- OAuth 1.0a User Context
- Tweets per request limits
- Endpoint URLs
- App and Project requirements
- Response data format
- Request parameters
OAuth 1.0a User Context authentication method
The standard endpoint supports OAuth 1.0a User Context, while the new Twitter API v2 Tweet lookup endpoint supports both OAuth 1.0a User Context and OAuth 2.0 Bearer Token. Therefore, if you were previously using one of the standard v1.1 Tweet lookup endpoints, you can continue using the same authentication method if you migrate to the Twitter API v2 version.
Depending on your authentication library/package of choice, Bearer Token authentication is probably the easiest way to get started and can be set with a simple request header. To learn how to generate a Bearer Token, see this OAuth 2.0 Bearer Token guide.
Tweets per request limits
The v1.1 GET statuses/lookup endpoint allows you to specify 100 Tweets per request. This also goes for the GET /tweets endpoint. To specify a full 100 Tweets, you will need to pass the ids parameter as a query parameter rather than a path parameter, and include the list of Tweet IDs in a comma-separated list.
- Standard v1.1 endpoints:
- Twitter API v2 endpoint:
App and Project requirements
The Twitter API v2 endpoints require that you use credentials from a developer App that is associated to a Project when authenticating your requests. All Twitter API v1.1 endpoints can use credentials from standalone Apps or Apps associated with a project.
Response data format
One of the biggest differences between standard v1.1 and Twitter API v2 endpoint versions is how you select which fields return in your payload.
For the standard endpoints, you receive many of the response fields by default, and then have the option to use parameters to identify which fields or sets of fields should return in the payload.
The Twitter API v2 version only delivers the Tweet id and text fields by default. To request any additional fields or objects, you wil need to use the fields and expansions parameters. Any Tweet fields that you request from these endpoints will return in the primary Tweet object. Any expanded user, media, poll, or place objects and fields will return in an includes object within your response. You can then match any expanded objects back to the Tweet object by matching the IDs located in both the Tweet and the expanded object.
We encourage you to read more about these new parameters in their respective guides, or by reading our guide on how to use fields and expansions.
We have also put together a data format migration guide which can help you map standard v1.1 fields to the newer v2 fields. This guide will also provide you the specific expansion and field parameter that you will need to pass with your v2 request to return specific fields.
- At the JSON root level, the standard endpoints return Tweet objects in a statuses array, while Twitter API v2 returns a data array.
- Instead of referring to Retweeted and Quoted "statuses", Twitter API v2 JSON refers to Retweeted and Quoted Tweets. Many legacy and deprecated fields, such as contributors and user.translator_type are being removed.
- Instead of using both favorites (in Tweet object) and favourites (in user object), Twitter API v2 uses the term like.
- Twitter is adopting the convention that JSON values with no value (for example, null) are not written to the payload. Tweet and user attributes are only included if they have a non-null values.
We also introduced a new set of fields to the Tweet object including the following:
- A conversation_id field
- Two new annotations fields, including context and entities
- Several new metrics fields
- A new reply_setting field, which shows you who can reply to a given Tweet
The following standard v1.1 request parameters have equivalents in Twitter API v2:
|Standard||Twitter API v2|
There are also a set of standard v1.1 Tweet lookup request parameters not supported in Twitter API v2:
|tweet_mode||This parameter enables developers to request a series of different extended fields that had been introduced in the years since statuses/show and statuses/lookup were introduced. It has been replaced with the fields and expansions functionality.|
|trim_user||This parameter is used to reduce the number of fields that deliver in the user object that comes alongside each Tweet. It has been replaced with the additive fields and expansions functionality.
To request user information alongside your requested Tweet, you will need to use a combination of the author_id expansion and the user.fields parameter with a set of specified user fields.
|include_my_retweet||This parameter includes the ID of the source Tweet for those specified Tweets that were Retweeted by the authenticating user.|
|include_entities||This parameter is used to remove the entities node from the Tweet payload. It has been replaced with the additive fields and expansions functionality.|
|include_ext_alt_text||This parameter adds an additional ext_alt_text field in the media entity if that media has alt text attached to it.
|include_card_uri||This parameters adds a card_uri attribute when there is an ads card attached.
This parameter would return the Tweet ID and nullified fields for unavailable Tweets.
In v2, we return the Tweet ID and a detailed error message for unavailable Tweets.