Comparing Twitter API’s List Tweets lookup endpoints
The v2 List Tweets lookup endpoint will replace the standard v1.1 GET lists/statuses. If you have code, apps, or tools that use this version of the 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 standard v1.1 and Twitter API v2 List endpoints:
List Lookup by ID
Description |
Standard v1.1 |
Twitter API v2 |
HTTP methods supported |
|
|
Host domain |
|
|
Endpoint path |
|
|
OAuth 1.0a User Context App only |
OAuth 1.0a User Context OAuth 2.0 Authorization Code with PKCE App only |
|
Default request rate limits |
900 requests per 15 min with OAuth 1.0a 900 requests per 15min with App only |
900 requests per 15 min with OAuth 1.0a 900 requests per 15 min with OAuth 2.0 900 requests per 15 min with App only |
To access the Twitter API v2 endpoints, you must sign up for a developer account. When authenticating, you must use keys and tokens from a developer App that is located within a Project.
Learn more about getting access to the Twitter API v2 endpoints in our getting started page.
