Manage List members: Standard v1.1 compared to Twitter API v2

If you have been working with the standard v1.1 POST lists/members/create and POST lists/members/destroy 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 members 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 List member 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/members/create.json
      (Adds a member to a specified List)
    • POST https://api.twitter.com/1.1/lists/members/destroy.json
      (Removes a member from a specified List)
  • Twitter API v2 endpoint:
    • POST https://api.twitter.com/2/lists/:id/members
      (Adds a member to a specified List)
    • DELETE https://api.twitter.com/2/lists/:id/members/:user_id
      (Removes a member from a specified List)

 

Rate limits

Standard v1.1 Twitter API v2

/1.1/lists/members/create.json

none

/2/lists/:id/members

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

/1.1/lists/members/destroy.json

none

/2/lists/:id/members/:user_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 that is 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:

 

Standard v1.1 Twitter API v2
list_id id
slug No equivalent
screen_name No equivalent
owner_screen_name No equivalent
owner_id No equivalent

Please note: The Standard v1.1 POST endpoint parameters are passed as query parameters. However, in Twitter API v2 , the POST method,id is passed as a path parameter and user_id as a body parameter and the DELETE method parameters are passed as path parameters.

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.