Comparing Twitter API’s Likes endpoints

These guides will focus on the following areas:

  • API request parameters - The Twitter API v2 endpoint introduces a new set of request parameters. While some parameters will be familiar, especially for those integrating with Labs, there are many important differences such as the introduction of the fields and expansions parameters.
  • App and Project requirements - To access the Twitter API v2, you will need to use credentials from a developer App that is associated with a Project

 

Manage Likes

The v2 manage Likes endpoints replace the v1.1 POST favorites/create and POST favorites/destroy endpoints.

The following tables compare the standard v1.1 and Twitter API v2 manage Like endpoints:

Like a Tweet

Description Standard v1.1 Twitter API v2
HTTP methods supported POST POST
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/favorites/create.json /2/users/:id/likes
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits 1000 requests per 15 min (per user)
1000 requests per 15 min (per App)
50 requests per 15 min (per user)
1000  (shared with DELETE) requests per 24 hours (per user)

 

Unlike a Tweet

Description Standard v1.1 Twitter API v2
HTTP methods supported POST DELETE
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/favorites/destroy.json /2/users/:id/likes/:tweet_id
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits 1000 requests per 15 min (per user)
1000 requests per 15 min (per App)
50 requests per 15 min (per user)
1000 (shared with POST) requests per 24 hours (per user)
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.