Manage Lists: Standard v1.1 compared to Twitter API v2

If you have been working with the standard v1.1 POST lists/create, POST lists/destroy, and POST lists/update endpoints, the goal of this guide is to help you understand the similarities and differences between the standard v1.1 and Twitter API v2 manage List endpoints.

  • Similarities
    • Authentication
  • Differences
    • Endpoint URLs
    • App and Project requirements
    • HTTP methods
    • Rate limits
    • Request parameters

 

Similarities

Authentication

Both endpoint versions support OAuth 1.0a User Context. Therefore, if you were previously using one of the standard v1.1 manage Lists endpoints, you can continue using the same authentication method if you migrate to the Twitter API v2 version.

 

Differences

Endpoint URLs

  • Standard v1.1 endpoints:
    • POST https://api.twitter.com/1.1/lists/create.json
      (Creates a List)
    • POST https://api.twitter.com/1.1/lists/destroy.json
      (Deletes a List)
    • POST https://api.twitter.com/1.1/lists/update.json
      (Updates a List)
  • Twitter API v2 endpoint:
    • POST https://api.twitter.com/2/lists
      (Creates a List)
    • DELETE https://api.twitter.com/2/lists/:id
      (Deletes a List)
    • PUT https://api.twitter.com/2/lists/:id
      (Updates a List)

Rate limits

Standard v1.1 Twitter API v2

/1.1/lists/create.json

none

/2/lists

300 requests per 15-minute window with OAuth 1.0a User Context

/1.1/lists/destroy.json

none

/2/lists/:id

300 requests per 15-minute window with OAuth 1.0a User Context

/1.1/lists/update.json

none

/2/lists/:id

300 requests per 15-minute window with OAuth 1.0a User Context

 

App and Project requirements

The Twitter API v2 endpoints require that you use credentials from a developer App associated with a Project when authenticating your requests. All Twitter API v1.1 endpoints can use credentials from standalone Apps or Apps related to a project.

 

Request parameters

The following standard v1.1 request parameters have equivalents in Twitter API v2:

Create a List

Standard Twitter API v2
name name
mode private
description description

 

Delete/Update a List

Standard Twitter API v2
owner_screen_name No equivalent
owner_id No equivalent
list_id id
slug No equivalent

Please note:

  •  Standard v1.1 parameters are passed as query parameters, whereas the Twitter API v2 parameters are passed as body parameters (for the POST endpoint) or path parameters (for the DELETE and PUT endpoints).
  • The URI in the location header from the POST request will lead to a 404 page until the lookup endpoints are released.
Was this document helpful?
Thank you

Thank you for the feedback. We’re really glad we could help!

Thank you for the feedback. How could we improve this document?
Thank you for the feedback. Your comments will help us improve our documents in the future.