The Twitter API has taken a winding road since its initial launch in 2006. Since 2012, Twitter has continued to clamp down on API consumption and usage, often to the dismay of the developer community. However, Twitter continues to understand the value of API features to its growth and the developer community. Yesterday it announced new endpoints to unleash more potential. The recently released Mute functionality now has corresponding API endpoints.
Similar to the blocks methods previously available, the Mute API endpoints allow a user to be “muted” from timelines of a user. While similar to “blocking” or “unfollowing”, the mute function allows users to temporarily suspend a user from timelines, and then unmute when desired. A nuanced difference, but muting presents a more subtle form of ignoring pests as users that have been muted are not notified.
Simple REST methods are used to mute and unmute users: POST/mutes/users/create, and POST/mutes/users/destroy. Additionally, developers can retrieve information on authenticated users and who such users are muting. For more information on Mute functionality, visit the help center.
Depending on the user, Twitter can be revolutionarily powerful, or painstakingly annoying. The Mute function brings new value to its controversial API as a subtle method of screening unwanted tweets. The Twitter team encourages developers to include the new endpoints in third party apps and tools. The new endpoints are rolling out this week.