Launched: Management API Versions 3.0 and 2.4

[Nick]

Hi,

Today we are releasing two new versions of our Management API into public beta; a brand new version 3.0 and a backwards compatible version 2.4. While the data the API exposes is the same, both versions migrate the Management API from the existing Google Data Protocol to Google’s new API infrastructure. This impacts the way you request and handle data from the API.

With this change, we are also announcing the deprecation of the legacy version 2.3 of the Management API. It will continue to work for 2 months, after which all v2.3 requests will return a v2.4 response.

The biggest changes in switching to the new versions are that developers need to register their applications via the Google APIs Console and use a developer token. Also the URL endpoints have changed, which influence how you request OAuth authorization tokens.

See the details on the Management API Changelog to see what's new.

If you're a developer, what you need to do

While we typically don’t share our roadmap, to alleviate any concerns, we wanted to give you some insight on where we’re going and how this release fits into the bigger picture. Today’s release adds two new versions to the Management API, v2.4 and v3.0. We also have a Data Export API that provides access to report data, which is still on version 2.3. In the future, we plan to do a similar upgrade to the Data Export API Data Feed by releasing two new versions for it, and deprecating version 2.3. At that time, we also plan to completely deprecate the Data Export API Account Feed.

The future of our APIs is to access all configuration data through the Management API and all processed report data through the Data Export API.

So for now, if you are already using the Management API, we recommend you migrate to the latest and greatest version 3.0.

If you are still using the Account Feed in the Data Export API, we highly recommend you test out the new Management API and start planning your migration. But, you can probably wait to do a full migration until all our APIs are on version 3.0.

Thanks,

-Nick