At the end of last week, third-party Twitter clients like Tweetbot and Twitterrific stopped working. The causes of the problem were unknown.however, this scenario was believed to be caused by two possible causes: a temporary failure or an API blockade.

Some of the doubts have been cleared and we know what’s going on. Twitter has limited access to its API, the set of protocols that developers use to access the social network’s features and data and use them in their own applications.

Twitter stops working on various third-party clients

This Tuesday night, it was the social network itself that recognized the movement through its developer profile. “Twitter itself rooted API rules. This may cause some apps to stop working.” stated in the message

The truth is, Twitter’s statement leaves a lot of doubt. Since it doesn’t link to “long-standing API rules”, there isn’t enough information to know what rules were violated or what could be wrong with certain apps requesting API access.

Message when opening Tweetbot on iOS

Apparently Twitter didn’t contact the developers and they just saw how their app works. they stopped working. In the case of Tweetbot, the company behind the app claims it tried to contact Twitter but didn’t get a response.

“We hope this is temporary,” they say. Of course, it should be noted that other applications such as Albatross and Fenix ​​continue to work normally, so the problems only affect some applications. For now, we know that access to the API is limited.

Images: twitter | tapbots | mawmy

On Xataka: Twitter shuts down Revue: Huge commitment to monetized newsletters ends less than two years later