Core Reporting API Migration Update
Back in December we launched the Core Reporting API to replace the Data Export API. We also announced that we would be shutting down the old Data Export API and that all applications should migrate to the new version.
The time has come for us to shut down the old version. So this is our last reminder to migrate to the new Core Reporting API.
Starting next week, we’ll begin redirecting a portion of Data Export API requests to the Core Reporting API as we prepare to shut down the Data Export API on July 10th. So you'll begin to see Data Feed requests return a Core Reporting API response, and requests for the Account Feed will produce an error.
If you do not migrate, your application will experience service outages.
For more information, visit:
Reminder: Migrate to the new Core Reporting API
Migration Guide: Moving from v2.3 APIs to v2.4 & v3.0
New Guides To Get You Started Fast
It’s important for the Google Analytics APIs to be open and accessible to all developers. It’s common practice for developers learning a new API to start off with the basics and incrementally build from this foundation.
So with that in mind, we wrote a new Hello Analytics API tutorial to give you that basic foundation. The tutorial includes sample code for Java, PHP, Python, and JavaScript. It also walks you through the basic steps of using the Google Analytics API, including registration, authorizing users, retrieving account and profile information, and querying for a report. Once complete you will have a working example that you can customize.
To make it even easier to build applications, we’ve also updated the developer guides for both the Core Reporting API and Management API. Examples for a variety of programming languages have been included, but more importantly the basic concepts have been highlighted.
So whether you’re just starting, updating, or migrating to the new version, you should check out the Hello Analytics API tutorial and Developer Guides before settling down to write that awesome application.
Posted by Pete Frisella, Nick Mihailovski, and Jeetendra Soneja, Analytics API team
