Skip to main content

Manage Lists: Standard v1.1 compared to X 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 X 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 X API v2 version.

Differences

Endpoint URLs Rate limits
Standard v1.1X 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 X API v2 endpoints require that you use credentials from a developer App associated with a Project when authenticating your requests. All X 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 X API v2: Create a List
StandardX API v2
namename
modeprivate
descriptiondescription
Delete/Update a List
StandardX API v2
owner_screen_nameNo equivalent
owner_idNo equivalent
list_idid
slugNo equivalent
Please note: Standard v1.1 parameters are passed as query parameters, whereas the X API v2 parameters are passed as body parameters (for the POST endpoint) or path parameters (for the DELETE and PUT endpoints).