Manage Posts endpoints migration overview

Move Post creation and deletion from Standard v1.1 statuses endpoints to X API v2 by comparing parameters, authentication, and rate limits.

Comparing X API’s manage Posts endpoints

The v2 manage Posts 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 Posts endpoints and are considering migrating to the newer X API v2 endpoint, then this set of guides is for you.

The following tables compare the standard v1.1 and X API v2 manage Posts endpoints:

Create a Post

Description	Standard v1.1	X API v2
HTTP methods supported	POST	POST
Host domain	https://api.x.com	https://api.x.com
Endpoint path	/1.1/statuses/update.json	/2/tweets
Authentication	OAuth 1.0a User Context	OAuth 1.0a User Context OAuth 2.0 Authorization Code with PKCE
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 Post

Description	Standard v1.1	X API v2
HTTP methods supported	POST	DELETE
Host domain	https://api.x.com	https://api.x.com
Endpoint path	/1.1/statuses/destroy/:id.json	/2/tweets/:id
Authentication	OAuth 1.0a User Context	OAuth 1.0a User Context OAuth 2.0 Authorization Code with PKCE
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		✔

Other migration resources

Manage Posts: Standard v1.1 to X API v2

X API migration hub