Comparing Twitter API’s Lists endpoints

The v2 manage Lists endpoints will eventually replace POST lists/createPOST lists/destroy, and POST lists/update. If you have code, apps, or tools that use an older version of these endpoints and are considering migrating to the newer Twitter API v2, then this guide is for you. 

The following tables compare the standard v1.1 and Twitter API v2 List endpoints:

 

Create a List

Description Standard v1.1 Twitter API v2
HTTP methods supported POST POST
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/lists/create.json /2/lists
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits None 300 requests per 15 min (per user)

 

Delete a List

Description Standard v1.1 Twitter API v2
HTTP methods supported POST DELETE
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/lists/destroy.json /2/lists/:id
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits None 300 requests per 15 min (per user)

 

Update a List

Description Standard v1.1 Twitter API v2
HTTP methods supported POST PUT
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/lists/update.json /2/lists/:id
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits None 300 requests per 15 min (per user)

 

 

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.