Comparing Twitter API’s manage Tweets endpoints

The v2 manage Tweets endpoints will replace the standard v1.1 POST statuses/update and POST statuses/destroy/:id endpoints. If you have code, apps, or tools that use the v1.1 version of the manage Tweets endpoints and are considering migrating to the newer Twitter API v2 endpoint, then this set of guides is for you. 

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

 

Create 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/statuses/update.json /2/tweets
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits

None

300 requests per 3-hour window per user, per app. Shared with the v1.1 POST Retweets endpoint.

200 requests per 15 min per user

300 requests per 3-hour window per user, per app. Shared with the v2 POST Retweets endpoint.

Requires the use of credentials from a developer App associated with a Project  


Delete 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/statuses/destroy/:id.json

 

/2/tweets/:id
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits None
50 requests per 15 min per user
Requires the use of credentials from a developer App associated with a Project