api February 10, 2014

Stack Exchange API V2.2 – and the demise of V1.x

There’s been a lot of excitement lately here at Stack Exchange, what with the launch of our Android app and the start of our iOS app alpha. A few sharp-eyed users noticed, hidden deep within each app, a new version of the Stack Exchange API. After a few more weeks of testing I’m happy to…
Avatar for Kevin Montrose
Team Lead, Data - Former

There’s been a lot of excitement lately here at Stack Exchange, what with the launch of our Android app and the start of our iOS app alpha. A few sharp-eyed users noticed, hidden deep within each app, a new version of the Stack Exchange API. After a few more weeks of testing I’m happy to say that V2.2 is now frozen, documented, and released.

What’s new in this release?

  • Creating questions and answers
  • Voting
  • Editing, Deleting, and Flagging
  • Improved OAuth UI on mobile devices
  • …and lots more

Almost everything done by our own apps is using our public API, but there are a few notable exceptions:

  • We don’t think the Feed is polished enough for inclusion yet
  • User creation is too sensitive to guarantee stability
  • Login methods that don’t use OAuth can’t be made public for security reasons

With the third release of the API V2.x family, we’ve decided to retire the V1.x family at long last. Version 1.0 of the Stack Exchange API was released in 2010, with its last update (V1.1) almost exactly three years ago, and its ultimate deprecation in 2012. Active consumers were notified of its imminent demise earlier this year, but this is the public announcement:

V1.0 and V1.1 of the Stack Exchange API will be shut down May 12th

I encourage anyone still using the V1.x family to use the coming months to migrate to V2.2. It’s much improved.

If you love the mobile trend, you can check out our listings for mobile developer jobs here.

Podcast logo The Stack Overflow Podcast is a weekly conversation about working in software development, learning to code, and the art and culture of computer programming.

Related

code-for-a-living July 21, 2021

Why you should build on Kubernetes from day one

If you’re building a new app today, it might be worth taking a closer look at making it cloud-native and using Kubernetes from the jump. The effort to set up Kubernetes is less than you think. Certainly, it’s less than the effort it would take to refactor your app later on to support containerization. 
company November 2, 2021

Our new and enhanced Microsoft Teams integration

With new features and tweaks to the Stack Overflow for Teams integration with Microsoft Teams, we’re sure that the new and improved Version 2 will come in handy. This article provides additional context around the evolution of this integration and how it might be useful to your organization!