Comparing Twitter API’s mutes endpoints

These guides will focus on the following areas:

  • New JSON format - Twitter API v2 introduces a completely new JSON format. Any code that parses v1.1 standard, premium, and enterprise JSON payloads will need to be updated to work with the new formats.
  • App and Project requirements - To access the Twitter API v2, you will need to use credentials from a developer App that is associated with a Project

 

Manage mutes

The v2 manage mutes endpoints will replace the standard v1.1 POST mutes/users/create and POST mutes/users/destroy endpoints.

The following tables compare the standard v1.1 and Twitter API v2 mute endpoints:

Mute a user

Description Standard v1.1 Twitter API v2
HTTP methods supported POST POST
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/mutes/users/create.json /2/users/:id/muting
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits 50 requests per 15 min 50 requests per 15 min

 

Unmute a user

The following tables compare the standard v1.1 and Twitter API v2 unmute endpoints:

Description Standard v1.1 Twitter API v2
HTTP methods supported POST DELETE
Host domain https://api.twitter.com https://api.twitter.com
Endpoint path /1.1/mutes/users/destroy.json /2/users/:source_user_id/muting/:target_user_id
Authentication OAuth 1.0a User Context OAuth 1.0a User Context
Default request rate limits 50 requests per 15 min 50 requests per 15 min
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.