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

If you have been working with the standard v1.1 POST lists/subscribers/create and POST lists/subscribers/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 follows endpoints.

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




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



Endpoint URLs

  • Standard v1.1 endpoints:
    • POST
      (Follow a List)
    • POST
      (Unfollow a List)
  • Twitter API v2 endpoint:
    • POST
      (Follow a List)
    • DELETE
      (Unfollow a List)


Rate limits

Standard v1.1 Twitter API v2




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




50 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 associated with a project.


Request parameters

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


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

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.