Please note:

We recently graduated hide replies into Twitter API v2: Early Access and announced a 90-day deprecation window. We will retire this endpoint in November 2020.

Learn more about the new hide replies endpoint, and review our migration resources to update to the new Twitter API.

Overview

Many people want the benefit of hiding replies to improve the quality of their conversations. Sometimes it’s difficult or overwhelming to do so without help, particularly when people receive a large number of replies, when those replies contain offensive or abusive language, or when they want to confine certain conversations to specific groups like close friends.

This endpoint gives you the ability to programmatically hide or unhide replies using criteria you define. Just like the functionality in the main Twitter experience, replies will be hidden from the main conversation but still visible on a separate page. You can use the endpoint to create apps to help people hide replies they don’t find valuable.

The hide replies endpoint uses OAuth 1.0a user context authentication. If successful, the endpoint hides a single Reply that was published in a Tweet conversation that was initiated by an authenticated user.

 


 

Additional resources

  • Get started building using the examples in the quick start guides
  • Check out our API reference to learn more about what’s available. 
  • Learn more about the new Developer Labs on the "About Labs" page. 
  • Give feedback on Twitter Developer Labs. 
  • Tell us about your experience using the Twitter Developer Labs endpoints by filling out this survey.

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.