Post, retrieve, and engage with Tweets

Please note:

We've recently released the following endpoints within the Twitter API v2 . The new version is currently in development and serves adequate access for the majority of developers on our platform. While elevated levels of access are coming to v2 soon, developers in need of higher levels of access either continue using the v1.1 versions, explore our v1.1 premium or enterprise APIs to see if one of those products will work with your use case, or review the v1.1 API reference to see if we offer an elevation. 

v1.1 endpoints Corresponding v2 endpoints  
GET statuses/lookup 
GET statuses/show/:id
Tweet lookup Comparison guide
GET favorites/list Likes lookup Comparison guide
POST favorites/create 
POST favorites/destroy
Manage Likes Comparison guide
GET statuses/retweets/:id 
GET statuses/retweeters/:ids
Retweets lookup Comparison guide
POST statuses/retweet/:id 
POST statuses/unretweet/:id
Manage Retweets Comparison guide

Please use the comparison guides to see what has changed between the standard v1.1 and v2 versions.

 

Overview

The following API endpoints can be used to programmatically create, retrieve and delete Tweets, Retweets and Likes:

Tweets Retweets Likes (formerly favorites)
  • POST statuses/update
  • POST statuses/destroy/:id
  • GET statuses/show/:id
  • GET statuses/oembed
  • GET statuses/lookup
  • POST statuses/retweet/:id
  • POST statuses/unretweet/:id
  • GET statuses/retweets/:id
  • GET statuses/retweets_of_me
  • GET statuses/retweeters/ids
  • POST favorites/create/:id
  • POST favorites/destroy/:id
  • GET favorites/list

For more details, please see the individual endpoint information within the API reference section.

Terminology

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'

Rate limits

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.