Comparing Twitter API’s List lookup endpoints

The v2 List lookup endpoint group will replace the standard v1.1 GET lists/show and  GET lists/ownership endpoints. If you have code, apps, or tools that use one of these versions of the List lookup endpoints, 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

GET

GET

Host domain

https://api.twitter.com

https://api.twitter.com

Endpoint path

/1.1/lists/show.json

/2/lists/:id

Authentication

OAuth 1.0a User Context

OAuth 2.0 Bearer Token

OAuth 1.0a User Context

OAuth 2.0 Bearer Token

Default request rate limits

75 requests per 15 min with OAuth 1.0a

75 requests per 15min with OAuth 2.0 Bearer Token

75 requests per 15 min with OAuth 1.0a

75 requests per 15 min with OAuth 2.0 Bearer Token

 

User owned List lookup

Description

Standard v1.1

Twitter API v2

HTTP methods supported

GET

GET

Host domain

https://api.twitter.com

https://api.twitter.com

Endpoint path

/1.1/lists/ownerships.json

/2/users/:id/owned_lists

Authentication

OAuth 1.0a User Context

OAuth 2.0 Bearer Token

OAuth 1.0a User Context

OAuth 2.0 Bearer Token

Default request rate limits

15 requests per 15 min with OAuth 1.0a

15 requests per 15min with OAuth 2.0 Bearer Token

15 requests per 15 min with OAuth 1.0a

15 requests per 15min with OAuth 2.0 Bearer Token

 

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.