The endpoints described in this section are the replacements of the v1.1 endpoints that allow you to manage muting relationships:

If you are currently using any of these endpoints, you can use our migration materials to start working with the new v2 versions.

Learn more about the new Twitter API v2: Early Access.


With manage mutes endpoints, developers can create safer experiences for people on Twitter. Muting an account allows you to remove an account's Tweets from your timeline without unfollowing or blocking that account. Muted accounts will not know that you've muted them and you can unmute them at any time.  One example of how to build with manage mutes is an application that allows you to mute accounts that might Tweet about specific topics for a specified length of time.

Because the manage mutes endpoints allow you to take action on behalf of a user, you must authenticate with OAuth 1.0a User Context.


Manage mutes

The manage mute endpoints enable you to mute or unmute a specified account on behalf of an authenticated user. For these endpoints, there are two methods available: POST and DELETE. The POST method allows you to mute an account, and the DELETE method allows you to unmute an account. There is a user rate limit of 50 requests per 15 minutes for both the POST and DELETE endpoints.

Please note: If a user mutes from Twitter, there is a limit of 200 requests per 15 minutes that will also count towards the 50 requests per 15 minutes on the POST endpoint.

To access these endpoints, you must have an approved developer account. When authenticating, you must use keys and tokens from a developer App that is located within a Project

Learn more about getting access to the Twitter API v2 endpoints in our getting started page.

Was this document helpful?
Thank you

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.