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

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

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

  • Similarities
    • OAuth 1.0a User Context
  • Differences
    • Endpoint URLs and HTTP methods
    • Request limitations
    • App and Project requirements
    • Request parameters



OAuth 1.0a User Context authentication method

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



Endpoint URLs and HTTP methods

  • Standard v1.1 endpoints:
    • POST
      (like a Tweet)
    • POST
      (unlike a Tweet)
  • Twitter API v2 endpoint:
    • POST
      (like a Tweet)
    • DELETE
      (unlike a Tweet) 


Request limitations

The v2 liked Tweets endpoint allows you to request 5 to 100 Tweets per request. You can use pagination tokens and multiple requests to get all of a user’s liked Tweets. The v1.1 GET favorites/list endpoint also allows you to pull all liked  Tweets, but you can pull from 20 to 200 Tweets per request.

For the v2 liking users endpoint, you are limited to 100 liking users per Tweet.

App and Project requirements

The Twitter API v2 endpoints require that you use credentials from a developer App that is associated to 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
id id
includes_entities No equivalent

Please note that the 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 endpoint.

Also, an id of the user liking a Tweet is not required when using the standard v1.1 endpoints since the Access Tokens passed with OAuth 1.0a User Context infer which user is initiating the like/unlike.