Comparing Twitter API’s hide replies endpoints

The v2 hide replies endpoint is replacing the Labs hide replies endpoint. If you have code, apps, or tools that use the Labs version of this endpoint, and are considering migrating to the newer Twitter API v2 endpoint, then this guide is for you.

In order to use the new Twitter API v2 (including the hide replies endpoint), you will need to opt in to the new developer portal, create a Project, and add an App to that Project. You can then use the credentials associated with that App to make requests to the hide replies endpoint. Adding the same App that's enrolled for the Labs v2 hide replies endpoint will keep your users authenticated.

The following table compares the differences between Labs and the newer Twitter API v2 endpoint:
 

Description Labs v2 Twitter API v2
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /labs/2/tweets/:id/hidden
/2/tweets/:id/hidden
Authentication OAuth 1.0a User context OAuth 1.0a User context
HTTP methods supported PUT
PUT
Default request rate limits 10 requests per 15 minutes (shared across all authenticated users) 50 requests per 15 min (for each authenticated user)
Can hide replies  ✔︎ ✔︎
Can unhide a previously hidden reply ✔︎ ✔︎
Can hide or unhide replies multiple times ✔︎ ✔︎

Other migration resources

Was this document helpful?

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.