Manage List members: Standard v1.1 compared to X 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 X 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 X API v2 version.Differences
Endpoint URLs- Standard v1.1 endpoints:
- POST https://api.x.com/1.1/lists/members/create.json (Adds a member to a specified List)
- POST https://api.x.com/1.1/lists/members/destroy.json (Removes a member from a specified List)
- X API v2 endpoint:
- POST https://api.x.com/2/lists/:id/members (Adds a member to a specified List)
- DELETE https://api.x.com/2/lists/:id/members/:user_id (Removes a member from a specified List)
| Standard v1.1 | X 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 300 requests per 15-minute window with OAuth 2.0 Authorization Code with PKCE |
| /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 300 requests per 15-minute window with OAuth 2.0 Authorization Code with PKCE |
| Standard v1.1 | X API v2 |
|---|---|
| list_id | id |
| slug | No equivalent |
| screen_name | No equivalent |
| owner_screen_name | No equivalent |
| owner_id | No equivalent |