Comparing Twitter API’s Tweets lookup endpoints

The v2 Tweets lookup endpoints will replace the standard v1.1 GET statuses/lookup and GET statuses/show endpoints, as well as the Labs Tweet lookup endpoints. If you have code, apps, or tools that use one of these versions of the Tweet lookup 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 Tweets lookup endpoints:
 

Description

Standard v1.1

Labs

Twitter API v2

HTTP methods supported

GET GET GET

Host domain

https://api.twitter.com https://api.twitter.com https://api.twitter.com

Endpoint path

/1.1/statuses/show.json /1.1/statuses/lookup.json /labs/2/tweets /2/tweets

Authentication

OAuth 1.0a User Context

OAuth 1.0a User Context

OAuth 2.0 Bearer Token

OAuth 1.0a User Context

OAuth 2.0 Bearer Token

Default request rate limits

Both
900 requests per 15 min per user

statuses/show
900 requests per 15 min per App

statuses/lookup
300 requests per 15 min per App

900 requests per 15 min

900 requests per 15 min per user

300 requests per 15 min per App

Maximum Tweets per response 

statuses/show -  1

statuses/lookup - 100

100

100

Tweet JSON format

Standard v1.1 format

Labs v2 (determined by fields and expansions request parameters, not backward-compatible with v1.1 formats)

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

 

Supports the annotations fields  
Supports requesting new metrics fields  
Supports the conversation_id field    
Requires the use of credentials from a developer App associated with a Project