- Accounts and users
- Direct Messages
- Publisher tools
- Twitter for Websites
- Developer utilities
- API reference index
The endpoints we release in Labs are previews and are likely to change before they are released broadly, so we encourage you to take that into consideration as you build. Before getting started, we encourage you to read more about Twitter Developer Labs.
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 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.
- 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.