Online Marketing Company, fishbat, Reacts to Twitter’s New API

Share Article

On August 16th, 2012 Twitter released information on the changes that will be made to version 1.1 of its API. These changes greatly affect third-party clients and the effect third-party clients will be able to have on the social media platform in the future.

On August 21st, 2012 online marketing company, fishbat, reacted to the news of Twitter’s API changes. The changes are meant to restrict what third-party Twitter applications can and can’t do.

Twitter’s Display Guidelines are now being called Display Requirements. This subtle change in language makes it clear that the list is no longer a suggestion. Developers who don’t follow Twitter’s Display Requirements run the risk of losing their application key.

Twitter is also limiting the amount of user tokens that developers have access to. Applications that access the Twitter timeline, account settings, or direct messaging API will be faced with a user cap of 100,000. Developers need to work directly with Twitter if they reach this limit and would have to seek certain permission to continue growing. Applications that are already in violation of this new change are still permitted to grow up until 200% of their user base as of August 16th.

Sida Li, Vice President of Internal Operations at online marketing company, fishbat, says, “This new set of API guidelines shows that Twitter is more serious than ever about taking control of its platform. They want to make sure that stylistically these apps reflect what Twitter is all about. I do foresee some backlash in their future though.”

Developers have six months to make any necessary changes before they face possible punishments.

Share article on social media or email:

View article via:

Pdf Print

Contact Author

Scott Darrohn
Email >
Visit website