We launched a new version of the following endpoints as part of Twitter API v2: Early Access:
|v1.1 endpoints||v2 replacement endpoints|
|statuses/lookup and statuses/show/:id||Tweet lookup||Migration guide|
|favorites/create and favorites/destroy||Manage Likes||Migration guide|
If you are currently using any of these endpoints, you can use our migration materials to start working with the newer endpoint.
The following API endpoints can be used to programmatically create, retrieve and delete Tweets, Retweets and Likes:
|Tweets||Retweets||Likes (formerly favorites)|
For more details, please see the individual endpoint information within the API reference section.
Tweet/Status - when a status message is shared on Twitter. Also see Introduction to Tweet JSON
Retweet - when a Tweet is re-shared by another specific user. Also see Introduction to Tweet JSON
Like - when a Tweet recieves a 'heart' from a specific user, formerly known as favo(u)rite or 'star'
As part of our effort to reduce the distribution of spam through our APIs, we enforce App-level rate limit on some of our POST endpoints:
- There is a 300 requests per three hours shared App-level rate limit for the POST statuses/update (post a Tweet) and POST statuses/retweet/:id (post a Retweet) endpoints. This means that you can only post either 300 Tweets or Retweets across all of the authorized users of your developer App during a three hour time period.
- There is a 1,000 requests per 24 hours App-level rate limit for the POST favorites/create/:id endpoint. This means that you can only like 1,000 Tweets across all of the authorized users of your developer App during a 24 hour time period.
Please note that you must also consider the user-level rate limits for these endpoints, as they limit the number of posted Tweets or liked Tweets a specific authorized user can make over a given time period.
You can review each endpoints' rate limits via their API reference page.