- Accounts and users
- Direct Messages
- Publisher tools & SDKs
- Twitter for Websites
- Developer utilities
- API reference index
Interested in exploring Labs?
The endpoints we release in Labs are previews of tools that may be released more broadly in the future, but will likely undergo changes before then. We encourage you to take that into consideration as you explore. Before getting started, please read more about Twitter Developer Labs.
Still using v1?
This page documents the current version of this endpoints, however you can still reference the previous version. You should also check out our version migration guide and review our changelog.
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.