The party is ON! Join us at TNW Conference 2021 in Amsterdam for face-to-face business!

Inside money, markets, and Big Tech

This article was published on June 10, 2009

Twitter developers be aware of OAuth API changes!

Twitter developers be aware of OAuth API changes!
Ralf
Story by

Ralf

Ralf Rottmann is a serial entrepreneur from Germany. He successfully sold his last business to Alcatel-Lucent. Follow him as @24z on Twitter Ralf Rottmann is a serial entrepreneur from Germany. He successfully sold his last business to Alcatel-Lucent. Follow him as @24z on Twitter and on Google+

love-twitterWe recently asked all Twitter third party app developers to get rid of asking for user credentials and kindly switch to delegated authentication based on the open OAuth protocol. Today we want to point you to some possible breaking API changes Twitter is going to implement within the next weeks:

As part of our changes for OAuth version 1.0a I have been looking at how this is going to work and there is going to need to be a change that will not be backward compatible. Some of this is already coded and waiting to go, and some of it is in-progress. I expect we will deploy this the end of next week or the beginning of the following one in order to allow you to have a minimum of 7 days to make changes. These only effect desktop applications so the majority of OAuth applications are not affected. (Source: Matt Samford, Engineer at Twitter)

More technical details and a discussion of the topic are available at the Twitter Development Talk Google group.

In case you wonder what this article’s image has to do with its contents? Well, nothing. We thought pimping the somewhat dry topic would make it a bit more enjoyable.