Création des Logiciels de gestion d'Entreprise, Création et référencement des sites web, Réseaux et Maintenance, Conception
seo Introducing the Multi-Channel Funnels Reporting API 2013
Seo Master present to you: 
By John Huang, Software Engineer
Cross-posted from the Google Analytics Blog
Measuring how marketing efforts influence conversions can be difficult, especially when your customers interact with multiple marketing channels over time before converting. Last fall, we launched Multi-Channel Funnels in Google Analytics, a new set of reports that help shed light on the full path users follow to conversion, rather than just the last click. One request we’ve had since the beginning was to make this data available via an API to allow developers to extend and automate use cases with the data. So today we’re releasing the new Google Analytics Multi-Channel Funnels Reporting API.
The API allows you to query for metrics like Assisted Conversions, First Interactions Conversions, and Last Interaction conversions, as well as Top Paths, Path Length and Time Lag, to incorporate conversion path data into your applications. Key use cases we’ve seen so far involve combining this conversion path data with other data sources, such as cost data, creating new visualizations, as well as using this data to automate processes such as bidding.
For example, Cardinal Path used the new Multi-Channel Funnels API, Analytics Canvas ETL (Extract, Transform, Load) and Tableau Software to help their client, C3 Presents, uncover how time and channels affected Lollapalooza ticket sales in an analysis dubbed “MCF DNA.” The outcome was a new visualization, similar to a DNA graph, that helped shed light on how channels appeared throughout the conversion funnel.
In another case, Mazeberry, an analytics company from France, helped their client 123Fleurs decrease customer acquisition costs by 20% by integrating data from the Multi-Channel Funnels API into a new reporting framework. Their application, Mazeberry Express, combines media cost and full conversion path data to provide new Cost Per Acquisition (CPA) and Return on Investment (ROI) metrics that provide a more complete understanding of how online channels are working together to influence conversions.
Please note that this functionality only works with the new v3.0 API libraries, so you should upgrade now if you haven’t already (see our migration guide). We look forward to seeing how you make use of this new data source.
John Huang is a Software Engineer working on Google Analytics. John is interested in all things analytics, mobile, and photography.
Posted by Scott Knaster, Editor2013, By: Seo Master
By John Huang, Software EngineerCross-posted from the Google Analytics Blog
Measuring how marketing efforts influence conversions can be difficult, especially when your customers interact with multiple marketing channels over time before converting. Last fall, we launched Multi-Channel Funnels in Google Analytics, a new set of reports that help shed light on the full path users follow to conversion, rather than just the last click. One request we’ve had since the beginning was to make this data available via an API to allow developers to extend and automate use cases with the data. So today we’re releasing the new Google Analytics Multi-Channel Funnels Reporting API.
The API allows you to query for metrics like Assisted Conversions, First Interactions Conversions, and Last Interaction conversions, as well as Top Paths, Path Length and Time Lag, to incorporate conversion path data into your applications. Key use cases we’ve seen so far involve combining this conversion path data with other data sources, such as cost data, creating new visualizations, as well as using this data to automate processes such as bidding.
For example, Cardinal Path used the new Multi-Channel Funnels API, Analytics Canvas ETL (Extract, Transform, Load) and Tableau Software to help their client, C3 Presents, uncover how time and channels affected Lollapalooza ticket sales in an analysis dubbed “MCF DNA.” The outcome was a new visualization, similar to a DNA graph, that helped shed light on how channels appeared throughout the conversion funnel.
 |
| MCF DNA Visualization in Tableu Software |
In another case, Mazeberry, an analytics company from France, helped their client 123Fleurs decrease customer acquisition costs by 20% by integrating data from the Multi-Channel Funnels API into a new reporting framework. Their application, Mazeberry Express, combines media cost and full conversion path data to provide new Cost Per Acquisition (CPA) and Return on Investment (ROI) metrics that provide a more complete understanding of how online channels are working together to influence conversions.
 |
| Mazeberry Express Screenshot - Focus on a Channel |
Please note that this functionality only works with the new v3.0 API libraries, so you should upgrade now if you haven’t already (see our migration guide). We look forward to seeing how you make use of this new data source.
John Huang is a Software Engineer working on Google Analytics. John is interested in all things analytics, mobile, and photography.
Posted by Scott Knaster, Editor2013, By: Seo Master
seo Get picky with the Google Picker API 2013
Seo Master present to you: 
By Chris Thrasher, Software Engineer, Google Picker API
Users have content across many Google properties: YouTube, Picasa Web Albums, Google Docs, and more. Now we have a common interface for your users to select Google content. The Google Picker API provides a familiar-looking dialog box that’s easy for you to integrate into your apps. Your users can quickly browse their own content without ever leaving your page or app.
Perhaps you’re developing a blogging platform and you want your users to be able to embed their Picasa Web Albums photos. You can even let your users pick from public content, as found from image and video search.
Once the Picker is invoked by your user, a modal dialog appears on the page. If the user is already signed in to their Google account, they’ll see their content in just a second or two. If not, the user will be asked to sign in.
Integrating with the Google Picker API is straightforward. First, you specify which Google services should show up as options in the Picker navigation. For example, if you’re a photo site, you may choose to show Picasa and Google Image Search, but hide Google Docs and other services. Then, you simply specify a callback function that will be called as soon as the user’s data is returned to your application.
Chris Thrasher is a Software Engineer at Google Kirkland and is part of the Google+ team. When he's not writing code, Chris is usually watching old movies. Or quoting from them.
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Chris Thrasher, Software Engineer, Google Picker API
Users have content across many Google properties: YouTube, Picasa Web Albums, Google Docs, and more. Now we have a common interface for your users to select Google content. The Google Picker API provides a familiar-looking dialog box that’s easy for you to integrate into your apps. Your users can quickly browse their own content without ever leaving your page or app.
Perhaps you’re developing a blogging platform and you want your users to be able to embed their Picasa Web Albums photos. You can even let your users pick from public content, as found from image and video search.
Once the Picker is invoked by your user, a modal dialog appears on the page. If the user is already signed in to their Google account, they’ll see their content in just a second or two. If not, the user will be asked to sign in.
Integrating with the Google Picker API is straightforward. First, you specify which Google services should show up as options in the Picker navigation. For example, if you’re a photo site, you may choose to show Picasa and Google Image Search, but hide Google Docs and other services. Then, you simply specify a callback function that will be called as soon as the user’s data is returned to your application.
var picker = new google.picker.PickerBuilder().You can find more integration details and examples in the documentation. We hope you enjoy this new API!
addView(google.picker.ViewId.IMAGE_SEARCH).
setCallback(pickerCallback).
build();
picker.setVisible(true);
Chris Thrasher is a Software Engineer at Google Kirkland and is part of the Google+ team. When he's not writing code, Chris is usually watching old movies. Or quoting from them.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Lightning fast! Performance tips for using Google APIs 2013
Seo Master present to you:
By Anton Lopyrev and Sven Mawson, Google Developer Team
Over a year ago, we launched support for partial response and partial update for a number of APIs based on the Google Data Protocol. That launch was a part of our continuous effort to make the web faster. It was well received by our developer community as it significantly reduced network, memory, and CPU resources needed to work with certain Google APIs.
Today, we are adding support for partial response and an improved version of partial update, called patch, to a number of newer APIs such as Buzz, URL Shortener, Tasks and many others. In fact, all APIs available in the Google APIs Discovery Service and the APIs Explorer now support this feature.
To learn how to use partial response and partial update with a Google API, you can see the “Performance Tips” page in the documentation of the Tasks and Buzz APIs. We’ll roll out this page for all of the supported APIs over the next few months, but you can already use the algorithms with all of them today.
The partial response algorithm is identical to what was provided by the Google Data Protocol. By supplying a
While the partial response algorithm is unchanged, the partial update algorithm has changed significantly compared to what was provided by Google Data Protocol. We’ve received feedback that the old algorithm was too complicated and hard to use, which prompted us to design something much simpler. The basics remain the same: you can use the HTTP
You can try out both partial response and patch algorithms in the APIs Explorer. For partial responses, the fields parameter is available for most methods. In addition, the partial update methods are denoted by
If you are using Java or Python client libraries to access Google APIs, you can already ask for partial responses and send patch requests in the code. We are adding partial support to the rest of the Google APIs client libraries over time.
As our APIs get more and more use from devices with limited resources, taking advantage of performance optimizations such as partial response and patch is crucial for making your applications faster and more efficient. By using these features in your applications, you are joining us in our effort to make the web faster. For this, we thank you! Let us know of any issues and feature requests by posting to the developer forums of your favorite APIs or by leaving a comment on this post. Happy hacking!
Anton Lopyrev is an Associate Product Manager for Google APIs Infrastructure. He is a computer graphics enthusiast who is also passionate about product design.
Sven Mawson is a Software Engineer working on Google’s API Infrastructure. He believes well-designed, beautiful APIs need not sacrifice performance.
Posted by Scott Knaster, Editor
2013, By: Seo Master
 |
| Sven |
 |
| Anton |
Over a year ago, we launched support for partial response and partial update for a number of APIs based on the Google Data Protocol. That launch was a part of our continuous effort to make the web faster. It was well received by our developer community as it significantly reduced network, memory, and CPU resources needed to work with certain Google APIs.
Today, we are adding support for partial response and an improved version of partial update, called patch, to a number of newer APIs such as Buzz, URL Shortener, Tasks and many others. In fact, all APIs available in the Google APIs Discovery Service and the APIs Explorer now support this feature.
To learn how to use partial response and partial update with a Google API, you can see the “Performance Tips” page in the documentation of the Tasks and Buzz APIs. We’ll roll out this page for all of the supported APIs over the next few months, but you can already use the algorithms with all of them today.
The partial response algorithm is identical to what was provided by the Google Data Protocol. By supplying a
fields query parameter to any API call that returns data, you can request specific fields. Here is an example request that returns only titles and timestamps of a user’s public Buzz activities:https://www.googleapis.com/buzz/v1/activities/antonlopyrev@gmail.com/@public?alt=json&pp=1&fields=items(title,updated)Given that the full response is around 53KB and the partial response is only 3KB, the data sent to the client is reduced by almost 95%!
While the partial response algorithm is unchanged, the partial update algorithm has changed significantly compared to what was provided by Google Data Protocol. We’ve received feedback that the old algorithm was too complicated and hard to use, which prompted us to design something much simpler. The basics remain the same: you can use the HTTP
PATCH verb in supported API methods to send partial updates to Google servers. However, the mechanics are different. Adding and modifying data uses the same 'merge' semantics as before. But deleting is simplified; just set a field to 'null'. Of course, the devil is in the details, so please check out the documentation for the nitty gritty.You can try out both partial response and patch algorithms in the APIs Explorer. For partial responses, the fields parameter is available for most methods. In addition, the partial update methods are denoted by
.patch in the method name. You can try both the fields parameter and the patch method on the “tasklist” resource in the APIs explorer. If you are using Java or Python client libraries to access Google APIs, you can already ask for partial responses and send patch requests in the code. We are adding partial support to the rest of the Google APIs client libraries over time.
As our APIs get more and more use from devices with limited resources, taking advantage of performance optimizations such as partial response and patch is crucial for making your applications faster and more efficient. By using these features in your applications, you are joining us in our effort to make the web faster. For this, we thank you! Let us know of any issues and feature requests by posting to the developer forums of your favorite APIs or by leaving a comment on this post. Happy hacking!
Anton Lopyrev is an Associate Product Manager for Google APIs Infrastructure. He is a computer graphics enthusiast who is also passionate about product design.
Sven Mawson is a Software Engineer working on Google’s API Infrastructure. He believes well-designed, beautiful APIs need not sacrifice performance.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo QR Codes now available on the Google Chart API 2013
Seo Master present to you:
You can easily render 2D bar codes, known as QR Codes, with the Google Chart API, along with pie charts and bar graphs. If you haven't seen a QR Code before, you are looking at one on the right hand side (To see more, do an image search for "QR Code".)
QR Codes are a popular type of two-dimensional barcode. You can encode URLs, contact information, etc. into a black-and-white image like the one on the right. A QR-Code-enabled device can later scan the image and read back the original text. Learn more about QR Codes from Google Print Ads. If you don't have a reader Google also offers a QR Code decoder library: Zebra Crossing (ZXing).
This is how you can creating these with the Google Chart API:
Simply, there is a new chart type,
<output> optionally specifies how the text is encoded into bytes in the QR Code. If this is not specified the default of
For the details, please read the full documentation.2013, By: Seo Master
You can easily render 2D bar codes, known as QR Codes, with the Google Chart API, along with pie charts and bar graphs. If you haven't seen a QR Code before, you are looking at one on the right hand side (To see more, do an image search for "QR Code".)QR Codes are a popular type of two-dimensional barcode. You can encode URLs, contact information, etc. into a black-and-white image like the one on the right. A QR-Code-enabled device can later scan the image and read back the original text. Learn more about QR Codes from Google Print Ads. If you don't have a reader Google also offers a QR Code decoder library: Zebra Crossing (ZXing).
This is how you can creating these with the Google Chart API:
Simply, there is a new chart type,
qr, with attributes to tell the service what to produce:cht=qr<text> is text for the QR code. This must be url-encoded in UTF8. Note the space between
chl=<text>
choe=<output>
hello and world is written as %20 in the following example.<output> optionally specifies how the text is encoded into bytes in the QR Code. If this is not specified the default of
UTF-8 is used. Available options are: Shift_JIS, UTF-8, or ISO-8859-1.For the details, please read the full documentation.2013, By: Seo Master
seo OAuth Available for Google Data APIs 2013
Seo Master present to you:
We love open standards, and we've just added support for a new one: OAuth is now supported on all of the Google Data APIs.
OAuth is an open standard for authentication that allows applications to authenticate users without ever directly handling usernames and passwords. Because OAuth is a standard, you can use the same authentication code for any of the Google Data APIs and for APIs from other providers who support OAuth.
To learn more, see the announcement on the Google Data APIs blog.2013, By: Seo Master
We love open standards, and we've just added support for a new one: OAuth is now supported on all of the Google Data APIs.
OAuth is an open standard for authentication that allows applications to authenticate users without ever directly handling usernames and passwords. Because OAuth is a standard, you can use the same authentication code for any of the Google Data APIs and for APIs from other providers who support OAuth.
To learn more, see the announcement on the Google Data APIs blog.2013, By: Seo Master
seo A Google Data API for Google Finance 2013
Seo Master present to you:
In case you haven't seen the announcement on the Google Data API blog, there is a new API available for Google Finance Portfolios.
The Google Finance API makes it easy to create and access investment data for your users -- ranging from updating their investment holdings and watchlists to retrieving current portfolio value and performance. With your applications, users can monitor their portfolios and transactions and keep positions up-to-date and in-sync. If you have a great idea for a portfolio application, give the new API a try!2013, By: Seo Master
In case you haven't seen the announcement on the Google Data API blog, there is a new API available for Google Finance Portfolios.
The Google Finance API makes it easy to create and access investment data for your users -- ranging from updating their investment holdings and watchlists to retrieving current portfolio value and performance. With your applications, users can monitor their portfolios and transactions and keep positions up-to-date and in-sync. If you have a great idea for a portfolio application, give the new API a try!2013, By: Seo Master
seo Check out the Custom Search API 2013
Seo Master present to you:
Have you ever wished that you could harness the power of Google to create a customized search engine for your website or a collection of websites? Custom Search lets you do that in under five minutes—and that includes time for a tea break. Pretty sweet, eh? If you have more time, you could take the customization to the next level. You can select websites to include, ignore, or prioritize in your search engine. You can even tweak the ranking of your search results and change the look and feel of your results page, among other things.
If you are curious about how tricked-out custom search engines work, you don't have to look further than the Custom Search API page on Google Code. Go ahead, try out some search queries and be sure to visit the Custom Search Directory, which showcases some popular custom search engines. And close to home, we use a combination of the Custom Search API and the AJAX Search API to power search on Google Code.2013, By: Seo Master
Have you ever wished that you could harness the power of Google to create a customized search engine for your website or a collection of websites? Custom Search lets you do that in under five minutes—and that includes time for a tea break. Pretty sweet, eh? If you have more time, you could take the customization to the next level. You can select websites to include, ignore, or prioritize in your search engine. You can even tweak the ranking of your search results and change the look and feel of your results page, among other things.
If you are curious about how tricked-out custom search engines work, you don't have to look further than the Custom Search API page on Google Code. Go ahead, try out some search queries and be sure to visit the Custom Search Directory, which showcases some popular custom search engines. And close to home, we use a combination of the Custom Search API and the AJAX Search API to power search on Google Code.2013, By: Seo Master
seo Another Round of Deprecation Policies for Labs Graduates 2013
Seo Master present to you: We recently published deprecation policies for a number of APIs that graduated from Google Code Labs. They state how long we'll support each version from when it's deprecated or a newer version is introduced. It will be 3 years for most, but the time period varies a bit from product to product.
We still need to update the terms for a couple remaining graduates, but should have them all done within the next couple weeks.
2013, By: Seo Master
- AdWords API terms
- AdSense API terms
- AJAX Feed API terms
- AJAX Language API terms
- AJAX Libraries API terms
- AJAX Search API terms
- Apps APIs terms
- Calendar Data API terms
- Chart API terms
- Health API terms
- Geo APIs terms (Earth API, Mapplets, Maps API, Maps API for Flash, and Static Maps API)
- Secure Data Connector terms
We still need to update the terms for a couple remaining graduates, but should have them all done within the next couple weeks.
2013, By: Seo Master
seo +1'ing our API docs 2013
Seo Master present to you: 
By Ashleigh Rentz, API Docs Program Manager
"Hey Scott, how do I format this API call so the data comes back as a string instead of an object?"
Sometimes it’s hard to find the right doc at the right time. Lots of web pages mention the terms you’re looking for, but which ones actually have them in the right context? We ask our friends and coworkers these questions because we bet they’ve seen the problem before. We trust their technical judgment and we know they can skip straight to the right answer.
That’s why we’ve just added the +1 button to the top of most code.google.com API docs:
Whenever you find the key information you need, we hope you’ll +1 that page and let the world know! It’s a simple way to help point the people you code with in the right direction and make RTFM’ing a bit easier for everyone.
Ashleigh Rentz is a Program Manager supporting the team of technical writers who tirelessly document Google’s developer APIs. She can often be seen skating down the halls between meetings.
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Ashleigh Rentz, API Docs Program Manager
"Hey Scott, how do I format this API call so the data comes back as a string instead of an object?"
Sometimes it’s hard to find the right doc at the right time. Lots of web pages mention the terms you’re looking for, but which ones actually have them in the right context? We ask our friends and coworkers these questions because we bet they’ve seen the problem before. We trust their technical judgment and we know they can skip straight to the right answer.
That’s why we’ve just added the +1 button to the top of most code.google.com API docs:
Whenever you find the key information you need, we hope you’ll +1 that page and let the world know! It’s a simple way to help point the people you code with in the right direction and make RTFM’ing a bit easier for everyone.
Ashleigh Rentz is a Program Manager supporting the team of technical writers who tirelessly document Google’s developer APIs. She can often be seen skating down the halls between meetings.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Making Google’s CalDAV and CardDAV APIs available for everyone 2013
Seo Master present to you: 
By Piotr Stanczyk, Tech Lead
In March we announced that CalDAV, an open standard for accessing calendar data across the web, would become a partner-only API because it appeared that almost all the API usage was driven by a few large developers. Since that announcement, we received many requests for access to CalDAV, giving us a better understanding of developers’ use cases and causing us to revisit that decision. In response to those requests, we are keeping the CalDAV API public. And in the spirit of openness, today we’re also making CardDAV – an open standard for accessing contact information across the web – available to everyone for the first time.
Both of these APIs are getting other updates as well:
https://apidata.googleusercontent.com/caldav/v2
Piotr Stanczyk is the Tech Lead of the Google Calendar APIs group. His current focus is to provide next generation Calendar APIs which make developers’ lives easier. He also participates in CalConnect consortium.
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Piotr Stanczyk, Tech LeadIn March we announced that CalDAV, an open standard for accessing calendar data across the web, would become a partner-only API because it appeared that almost all the API usage was driven by a few large developers. Since that announcement, we received many requests for access to CalDAV, giving us a better understanding of developers’ use cases and causing us to revisit that decision. In response to those requests, we are keeping the CalDAV API public. And in the spirit of openness, today we’re also making CardDAV – an open standard for accessing contact information across the web – available to everyone for the first time.
Both of these APIs are getting other updates as well:
- Integration with the Google APIs Console. To start using CalDAV or CardDAV in your project, just enable it in the Console.
- OAuth 2.0 authentication.
https://apidata.googleusercontent.com/caldav/v2
Piotr Stanczyk is the Tech Lead of the Google Calendar APIs group. His current focus is to provide next generation Calendar APIs which make developers’ lives easier. He also participates in CalConnect consortium.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Spring cleaning for some of our APIs 2013
Seo Master present to you: 
By Adam Feldman, APIs Product Manager
UPDATE June 3: In the days since we announced the deprecation of the Translate API, we’ve seen the passion and interest expressed by so many of you, through comments here (believe me, we read every one of them) and elsewhere. I’m happy to share that we’re working hard to address your concerns, and will be releasing an updated plan to offer a paid version of the Translate API. Please stay tuned; we’ll post a full update as soon as possible.
Google I/O is always an exciting time for developers. This year we made 34 separate announcements, including 7 new APIs:
As the web evolves and priorities change, we sometimes deprecate APIs – that is, remove them from active development – to free up resources and concentrate on moving forward. Today we're announcing a spring cleaning for some of our APIs.
Note that the vast majority of Google APIs are not affected by this announcement.
Following the standard deprecation period – often, as long as three years – some of the deprecated APIs will be shut down. The rest have no scheduled date for shutdown, but won’t get any new features. The policy for each deprecated API is specified in its documentation.
Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Adam Feldman, APIs Product Manager
UPDATE June 3: In the days since we announced the deprecation of the Translate API, we’ve seen the passion and interest expressed by so many of you, through comments here (believe me, we read every one of them) and elsewhere. I’m happy to share that we’re working hard to address your concerns, and will be releasing an updated plan to offer a paid version of the Translate API. Please stay tuned; we’ll post a full update as soon as possible.
Google I/O is always an exciting time for developers. This year we made 34 separate announcements, including 7 new APIs:
- Discovery Service
- Tasks API
- Books API
- Pagespeed Online API
- Places API (now generally available)
- Prediction API (now generally available)
- Fusion Tables API (additional feeds)
As the web evolves and priorities change, we sometimes deprecate APIs – that is, remove them from active development – to free up resources and concentrate on moving forward. Today we're announcing a spring cleaning for some of our APIs.
Note that the vast majority of Google APIs are not affected by this announcement.
Following the standard deprecation period – often, as long as three years – some of the deprecated APIs will be shut down. The rest have no scheduled date for shutdown, but won’t get any new features. The policy for each deprecated API is specified in its documentation.
- These APIs are now deprecated but have no scheduled shutdown date: Code Search API, Diacritize API, Feedburner APIs, Finance API, Power Meter API, Sidewiki API, Wave API
- These APIs will be shut down as per their deprecation policies: Blog Search API, Books Data API and Books JavaScript API (not the new API), Image Search API, News Search API, Patent Search API, Safe Browsing API (v1 only), Translate API, Transliterate API, Video Search API, Virtual Keyboard API
Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Upgrade now to the new Google Analytics Core Reporting API 2013
Seo Master present to you:
By Pete Frisella, Nick Mihailovski, and Jeetendra Soneja, Google Analytics API Team
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.
Pete Frisella is a Developer Advocate for Google Analytics, interested in encouraging and promoting awesome Google Analytics integrations. Pete loves to talk tech, travel, and hit the golf course when he can.
Nick Mihailovski is a Senior Developer Programs Engineer working on the Google Analytics API. In his spare time he likes to travel around the world.
Jeetendra Soneja is the Technical Engineering Lead on the Google Analytics API team. He's a big fan of cricket – the game, that is. :)
Posted by Scott Knaster, Editor
2013, By: Seo Master
 |
| Jeetendra |
 |
| Nick |
 |
| Pete |
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.
Pete Frisella is a Developer Advocate for Google Analytics, interested in encouraging and promoting awesome Google Analytics integrations. Pete loves to talk tech, travel, and hit the golf course when he can.
Nick Mihailovski is a Senior Developer Programs Engineer working on the Google Analytics API. In his spare time he likes to travel around the world.
Jeetendra Soneja is the Technical Engineering Lead on the Google Analytics API team. He's a big fan of cricket – the game, that is. :)
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo The Google APIs Explorer has a new look 2013
Seo Master present to you:
By Antonio Fuentes and Jake Moshenko,
Google Developer Team
Last March we introduced the Google APIs Explorer, an interactive tool that enables you to try out a Google API in minutes and explore its supported methods. When we launched it, the APIs Explorer supported over a half dozen APIs.
Starting today, the APIs Explorer has a brand new look to make it easier and more fun to navigate. We are also adding new features, including an indexed history of your API calls, a better editor for the body of a request, and a search box so you can search for APIs and methods easily.
Moreover, we have been busy adding support for more APIs to the Explorer. The Explorer now supports over two dozen Google APIs, and the list continues to grow! We have also added an indicator to show which methods require authenticated requests.
To get started, here are some sample requests you can try in the Explorer:
The APIs Explorer will help you get started using Google APIs in minutes. If you need more information, visit the documentation. We always welcome your feedback in the Public Forum.
Antonio Fuentes is a Product Manager focusing on developer-facing technologies.
Jake Moshenko is a Software Engineer working on the Google APIs developer experience. He believes that Google APIs should be easy to use, especially from Google platforms.
Posted by Scott Knaster, Editor
2013, By: Seo Master
 |
| Jake |
 |
| Antonio |
Google Developer Team
Last March we introduced the Google APIs Explorer, an interactive tool that enables you to try out a Google API in minutes and explore its supported methods. When we launched it, the APIs Explorer supported over a half dozen APIs.
Starting today, the APIs Explorer has a brand new look to make it easier and more fun to navigate. We are also adding new features, including an indexed history of your API calls, a better editor for the body of a request, and a search box so you can search for APIs and methods easily.
Moreover, we have been busy adding support for more APIs to the Explorer. The Explorer now supports over two dozen Google APIs, and the list continues to grow! We have also added an indicator to show which methods require authenticated requests.
To get started, here are some sample requests you can try in the Explorer:
- Use the Google+ API to search for public profiles of people named "John Smith".
- Use the Books API to search for a particular book.
- Use the Google+ API to list your personal Google+ activities (requires private access).
The APIs Explorer will help you get started using Google APIs in minutes. If you need more information, visit the documentation. We always welcome your feedback in the Public Forum.
Antonio Fuentes is a Product Manager focusing on developer-facing technologies.
Jake Moshenko is a Software Engineer working on the Google APIs developer experience. He believes that Google APIs should be easy to use, especially from Google platforms.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Introducing the Google Buzz API 2013
Seo Master present to you: With Google I/O 2010 finally upon us, what better time to introduce developers to the latest updates to the Google Buzz API?
As announced at the launch of Google Buzz, the Google Buzz API aligns itself with the ever-growing family of freely available and community-developed protocols, formats, and standards for sharing and consuming social content on the web, including ActivityStreams, Atom, AtomPub, JSON, OAuth, PubSubHubbub, MediaRSS, PortableContacts, and more.
The Google Buzz API, a member of the Google Code Labs, is very much a work in progress — we intend to continue to iterate out in the open as we go along — and we hope the features we are making available today will help inspire developers and provide a solid foundation for new applications to be built.
We are already excited to see developers who were helping us test the API deliver terrific applications. Today you'll start seeing the following sites and services integrate with Google Buzz:
End-users opt into using applications built with the Google Buzz API via an interstitial confirmation screen outlining the application's requested access scope (read-only, read/write, etc.). They can see which apps have access to their data and can disable access at any time from the Google Accounts page, the Google Dashboard, the “Buzz" tab in Gmail Settings, or from the app itself.
This initial iteration of the API includes support for fetching public per-user activity feeds, fetching authorized and authenticated per-user activity feeds (both what the user creates, and what they see), searching over public updates (by keyword, by author, and by location), posting new updates (including text, html, images, and more), posting comments, liking updates, retrieving and updating profiles and social graphs, and more. The best way to get started is to dive right in and begin reading the Google Buzz API developer documentation.
There’s a lot more to come, and we expect to keep moving quickly from here. But none of this would be possible without the hard work of everyone participating in creating the protocols upon which Google Buzz is built, so we ask and encourage developers to get involved with the communities behind ActivityStreams, OAuth, and the countless others that we depend on.
And as with any young API, there will undoubtedly be bugs and issues and places where we’ve deviated from what the specifications say, or with what developers may expect. When you see something amiss, get confused by an approach we’ve taken, or just want to comment on our progress, we invite you to update the Buzz API issue tracker and please join the conversation on the developer forum.
With that, we’d like to welcome everyone to the first version of the Google Buzz API. We can’t wait to see what else we can build together.
By DeWitt Clinton, Google Developer Team2013, By: Seo Master
As announced at the launch of Google Buzz, the Google Buzz API aligns itself with the ever-growing family of freely available and community-developed protocols, formats, and standards for sharing and consuming social content on the web, including ActivityStreams, Atom, AtomPub, JSON, OAuth, PubSubHubbub, MediaRSS, PortableContacts, and more.
The Google Buzz API, a member of the Google Code Labs, is very much a work in progress — we intend to continue to iterate out in the open as we go along — and we hope the features we are making available today will help inspire developers and provide a solid foundation for new applications to be built.
We are already excited to see developers who were helping us test the API deliver terrific applications. Today you'll start seeing the following sites and services integrate with Google Buzz:
End-users opt into using applications built with the Google Buzz API via an interstitial confirmation screen outlining the application's requested access scope (read-only, read/write, etc.). They can see which apps have access to their data and can disable access at any time from the Google Accounts page, the Google Dashboard, the “Buzz" tab in Gmail Settings, or from the app itself.
This initial iteration of the API includes support for fetching public per-user activity feeds, fetching authorized and authenticated per-user activity feeds (both what the user creates, and what they see), searching over public updates (by keyword, by author, and by location), posting new updates (including text, html, images, and more), posting comments, liking updates, retrieving and updating profiles and social graphs, and more. The best way to get started is to dive right in and begin reading the Google Buzz API developer documentation.
There’s a lot more to come, and we expect to keep moving quickly from here. But none of this would be possible without the hard work of everyone participating in creating the protocols upon which Google Buzz is built, so we ask and encourage developers to get involved with the communities behind ActivityStreams, OAuth, and the countless others that we depend on.
And as with any young API, there will undoubtedly be bugs and issues and places where we’ve deviated from what the specifications say, or with what developers may expect. When you see something amiss, get confused by an approach we’ve taken, or just want to comment on our progress, we invite you to update the Buzz API issue tracker and please join the conversation on the developer forum.
With that, we’d like to welcome everyone to the first version of the Google Buzz API. We can’t wait to see what else we can build together.
By DeWitt Clinton, Google Developer Team2013, By: Seo Master
seo Hangouts Hackathon: 1 API, 5 developers, 2 weeks 2013
Seo Master present to you: By Jonathan Beri, Google+ Developer Advocate
Cross-posted from the Google+ Developers Blog
Last week we released an update to the Google+ Hangouts API, which includes several new features and possibilities to build on, like the ability to respond to facial movements in real-time inside an app.
As with any new API, we’re especially interested in what sorts of things our developer friends will dream up, so we've commissioned a handful of them to play with it over the next couple of weeks, and to share their thoughts and discoveries along the way. The participants represent a wide range of developers -- from agencies like The Barbarian Group to independent developers like Eyebeam alum Aaron Meyers teamed up with OKFocus.
Follow the Hangouts Hackathon with us on the Google+ Developers page, and, if you’re working on an interesting Hangouts API project we’d love to hear about that too. Use hashtag #hangoutshackathon to chat about our work, or your own, with the new API.
2013, By: Seo Master
Cross-posted from the Google+ Developers Blog
Last week we released an update to the Google+ Hangouts API, which includes several new features and possibilities to build on, like the ability to respond to facial movements in real-time inside an app.
As with any new API, we’re especially interested in what sorts of things our developer friends will dream up, so we've commissioned a handful of them to play with it over the next couple of weeks, and to share their thoughts and discoveries along the way. The participants represent a wide range of developers -- from agencies like The Barbarian Group to independent developers like Eyebeam alum Aaron Meyers teamed up with OKFocus.
Follow the Hangouts Hackathon with us on the Google+ Developers page, and, if you’re working on an interesting Hangouts API project we’d love to hear about that too. Use hashtag #hangoutshackathon to chat about our work, or your own, with the new API.
2013, By: Seo Master
seo Find the hidden patterns with YouTube’s new Analytics API 2013
Seo Master present to you: 
By Ted Hamilton, YouTube Analytics
Cross-posted from the YouTube API Blog
Trying to figure out how YouTube’s one billion monthly users are interacting with your videos? Try the new YouTube Analytics API to get custom reports of the YouTube statistics you care about in a direct JSON or CSV response, perfect for dashboards and ad hoc reports.
The new API includes all the standard view and engagement metrics you would expect, including views, shares, and subscriber numbers. Compared to the previous Insight Data API, you also get:
You’ll find client libraries for the languages you use most, with nine different languages available today. You can also make HTTP RESTful requests directly, and with our API Explorer, you can try out sample reports before writing any code.
Don’t write your code from scratch! Get started with code examples in Java, JavaScript, Python, and Ruby. If you want a step-by-step walkthrough of building a complete web application, have a look at our JavaScript exercise.
App examples
Check out some apps that are already using the API:
Fullscreen is building a global network of YouTube channels with content creators and brands. Fullscreen provides a full suite of end-to-end YouTube tools and uses the new API for internal, business-intelligence tools.
Learn more
In addition to the documentation, check out our Analytics API playlist to make getting started even easier.
If your goal is to export all statistics for a large number of channels on a recurring basis for your data warehouse, look forward to using the upcoming scheduled reports feature of the API, expected to launch later this year.
To get more info on the YouTube APIs, subscribe to our YouTube for Developers channel and YouTubeDev on Google+.
Ted Hamilton is the Product Manager for YouTube Analytics based out of Zurich, Switzerland. Prior to Google, Ted was a consultant at Bain and Company in London. Ted has a Computer Science degree from Northwestern University and holds an MBA from MIT Sloan.
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Ted Hamilton, YouTube AnalyticsCross-posted from the YouTube API Blog
Trying to figure out how YouTube’s one billion monthly users are interacting with your videos? Try the new YouTube Analytics API to get custom reports of the YouTube statistics you care about in a direct JSON or CSV response, perfect for dashboards and ad hoc reports.
The new API includes all the standard view and engagement metrics you would expect, including views, shares, and subscriber numbers. Compared to the previous Insight Data API, you also get:
- Watch metrics: Track estimated minutes watched across channel, content owner, or video, and dive into the video details with average view time and average view percentage.
- Earning performance metrics: Track estimated earnings (net revenue) from select advertising sources across your content.
- Ad performance metrics: Break down video performance with monetized playbacks, ad impressions, gross revenue, and cost per impression reports.
- Annotation metrics: Optimize overlays/annotations with click through and close rate metrics.
You’ll find client libraries for the languages you use most, with nine different languages available today. You can also make HTTP RESTful requests directly, and with our API Explorer, you can try out sample reports before writing any code.
Don’t write your code from scratch! Get started with code examples in Java, JavaScript, Python, and Ruby. If you want a step-by-step walkthrough of building a complete web application, have a look at our JavaScript exercise.
App examples
Check out some apps that are already using the API:
- Next Big Sound provides analytics and insights for the music industry by tracking billions of social signals including YouTube. This enables record labels, artists, and band managers to make better decisions on everything from promotion strategies to tour locations.
- vidIQ is an audience development suite that works with global brands to organically grow their views and subscribers. Their features include cross-platform social analytics, advanced comment management, SEO tools, social syndication and influencer identification.
- Wizdeo’s WizTracker provides in-depth analysis of YouTube channels to help with cross promotion and video comparisons during their initial launch. Users get access to detailed analytics about views, subscriber engagement, traffic sources and demographics.
- Vidyard is a video marketing platform. With powerful analytics, built-in marketing tools, and integration with key marketing automation platforms, Vidyard helps marketers drive results with video content.
Learn more
In addition to the documentation, check out our Analytics API playlist to make getting started even easier.
If your goal is to export all statistics for a large number of channels on a recurring basis for your data warehouse, look forward to using the upcoming scheduled reports feature of the API, expected to launch later this year.
To get more info on the YouTube APIs, subscribe to our YouTube for Developers channel and YouTubeDev on Google+.
Ted Hamilton is the Product Manager for YouTube Analytics based out of Zurich, Switzerland. Prior to Google, Ted was a consultant at Bain and Company in London. Ted has a Computer Science degree from Northwestern University and holds an MBA from MIT Sloan.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Getting organized with the Tasks API 2013
Seo Master present to you:
Client libraries are provided for several major programming environments and should help you get up and running quickly.
The API is available in Labs and can be activated for your project through the API Console. Get started today by trying the Tasks API yourself using the API Explorer and taking a look at the documentation.
If you want to see the API in action check out the Google Tasks Chrome Extension. If you are at Google I/O we invite you to come along and hear the Google Tasks team talk about the new API today.
We thank the early adopters that have worked with us and built their own Google Tasks integrations over the last weeks. We’d like to highlight a few of them:
Get Started with the Google Tasks API today!
2013, By: Seo Master
Cross-posted from the Google Apps Developer Blog
Today, we’re checking off a big to-do from our list and are inviting you to try out the new Google Tasks API. Using the Google Tasks API, developers can — for the very first time — create rich applications which integrate directly with Google Tasks.
The Google Tasks API provides developers with a powerful set of API endpoints for retrieving and modifying Google Tasks content and metadata. It offers a simple, RESTful interface and supports all basic operations required to query, manage and sync a user’s tasks and task lists. The API uses JSON for data representation and works with multiple authentication mechanisms including OAuth 2.0.
| Plain HTTP using JSON | Using Google API Client Library for Java |
POST /tasks/v1/lists/<list-ID>/tasks | Task task = new Task(); |
The API is available in Labs and can be activated for your project through the API Console. Get started today by trying the Tasks API yourself using the API Explorer and taking a look at the documentation.
If you want to see the API in action check out the Google Tasks Chrome Extension. If you are at Google I/O we invite you to come along and hear the Google Tasks team talk about the new API today.
We thank the early adopters that have worked with us and built their own Google Tasks integrations over the last weeks. We’d like to highlight a few of them:
- Producteev is a task management platform that lets teams and individuals access their to-dos from a lot of different locations (web, mobile, email, calendars...). You will now have all your Producteev's tasks available in Google Tasks and vice versa!
- Mavenlink's project collaboration suite allows you to communicate, share files, track time, invoice, and make or receive payments in one place. With its Google Tasks integration, your Mavenlink project tasks & Google Tasks always stay in sync.
- Manymoon is the top installed social task and project management app in the Google Apps Marketplace and makes it simple to get work done online with co-workers, partners, and customers. Manymoon's users can now create and view tasks with Gmail and Google Calendar through Google Tasks.
- Zoho offers a suite of online business, collaboration and productivity applications for small businesses. So far they have integrated Zoho CRM & Zoho Projects with the Tasks API.
Get Started with the Google Tasks API today!
Want to weigh in on this topic? Discuss on Buzz
  | Posted by Fabian Schlup & Nicolas Garnier Google Tasks API Team |
seo Google Prediction API helps all apps to adapt and learn 2013
Seo Master present to you: 
By Travis Green, Product Manager
Now your apps can get smarter with as little as a single line of code. They can learn to continually adapt to changing conditions and to integrate new information. This week at Google I/O, we’re making the Google Prediction API generally available, meaning you can create apps with these capabilities for yourself. Additionally, we’re introducing several significant new features, including:
Here’s a summary of the features we added to the API today:
Thanks to our community of preview developers, who have played a crucial role in helping us make the Google Prediction API simpler and more powerful since its announcement last year at I/O 2010. We are thrilled to invite all developers to join them.
Travis Green's favorite part about his job is designing smart applications. In his spare time, he is in the great outdoors (looking for trouble).
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Travis Green, Product Manager
Now your apps can get smarter with as little as a single line of code. They can learn to continually adapt to changing conditions and to integrate new information. This week at Google I/O, we’re making the Google Prediction API generally available, meaning you can create apps with these capabilities for yourself. Additionally, we’re introducing several significant new features, including:
- The ability to stream data and tune your predictive models
- A forthcoming gallery of user-developed, pre-built models to add smarts even faster.
- Recommend a new movie to a customer.
- Identify most important customers.
- Automatically tag posts with relevant flags.
Here’s a summary of the features we added to the API today:
- Streaming training data: Continually incorporate feedback for fast-adapting systems (e.g. user-chosen tags vs predicted ones, final purchases vs expected).
- General availability: Anyone can now sign up to use the API. Paid users also receive a 99.9% SLA with increased quota.
- New JavaScript library: Now deploy the Prediction API in your JavaScript – in addition to our updated Python and Java libraries.
- Subscribe to others’ models: improve your apps with others’ predictive data tools.
- Sell access to your models (e.g. sentiment analysis on social media).
- Import customized models through the open-standard PMML encoding.
Thanks to our community of preview developers, who have played a crucial role in helping us make the Google Prediction API simpler and more powerful since its announcement last year at I/O 2010. We are thrilled to invite all developers to join them.
Travis Green's favorite part about his job is designing smart applications. In his spare time, he is in the great outdoors (looking for trouble).
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Clarifying the deprecation policy for Google APIs and services 2013
Seo Master present to you: 
By Adam Feldman, APIs Product Manager
We know that deprecation policies can be complex. But it shouldn’t be hard for you to determine which features of our APIs and services are covered by a deprecation policy and which ones aren’t. To date, we’ve often used the label “Experimental” to indicate that certain new versions, features, or functionality don’t have the deprecation policy. But we know you don’t want to hunt through documentation looking for what is “Experimental” and what isn’t.
So starting today, for each API or service that has the deprecation policy, we are creating an explicit list of what is covered by that policy. For instance, here’s what this list will look like for the Google Maps APIs:
We are not adding or subtracting anything, but only changing how we display this information to make it easier to locate and understand. This change will be fully rolled out in the coming weeks. Please refer to each API or service’s terms of service for more information. We hope this will make your life easier so you get back to your code sooner!
Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.
Posted by Scott Knaster, Editor
2013, By: Seo Master
By Adam Feldman, APIs Product Manager
We know that deprecation policies can be complex. But it shouldn’t be hard for you to determine which features of our APIs and services are covered by a deprecation policy and which ones aren’t. To date, we’ve often used the label “Experimental” to indicate that certain new versions, features, or functionality don’t have the deprecation policy. But we know you don’t want to hunt through documentation looking for what is “Experimental” and what isn’t.
So starting today, for each API or service that has the deprecation policy, we are creating an explicit list of what is covered by that policy. For instance, here’s what this list will look like for the Google Maps APIs:
Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.
Posted by Scott Knaster, Editor
2013, By: Seo Master
seo Google APIs Discovery Service: one API to find them all 2013
Seo Master present to you:
By Anton Lopyrev, Monsur Hossain, and Joe Gregorio, Google Developer Team
As announced at last Google I/O, the new family of Google APIs client libraries runs on top of a brand new API infrastructure, which allows Google to reduce the amount of work needed to release and maintain the client libraries. This is done through a simple API that provides machine readable descriptions of Google APIs that the client libraries take advantage of.
Today, we are announcing the Google APIs Discovery Service, which is the secret sauce behind the new client libraries. This service exposes machine readable metadata about Google APIs including:
You can use the APIs Discovery Service to build tools for interacting with Google APIs, such as IDE Plugins and client libraries. We use the service at Google to build a number of such tools:
Read more about Google APIs Discovery Service in the documentation, or explore its API in the APIs Explorer. If you are attending this year’s Google I/O and you want to know more about the service, make sure to attend our session “Building Custom Client Libraries for Google APIs” where you can chat with the developers of the service face-to-face.
We look forward to seeing what sorts of things you can build. Let us know of any issues and feature requests in our developer forum. Happy hacking!
Anton Lopyrev is an Associate Product Manager for Google APIs Infrastructure, previously a software engineer on Street View. He is a computer graphics enthusiast who is also passionate about product design.
Joe Gregorio is a Software Engineer. In the past four years at Google he’s worked on APIs, Google App Engine, Google Wave, and now has come full circle and is back working on APIs.
Monsur Hossain is a Software Engineer for Google APIs Infrastructure and enjoys making it easier to use APIs.
Posted by Scott Knaster, Editor
2013, By: Seo Master
 |
| Anton |
 |
| Monsur |
 |
| Joe |
As announced at last Google I/O, the new family of Google APIs client libraries runs on top of a brand new API infrastructure, which allows Google to reduce the amount of work needed to release and maintain the client libraries. This is done through a simple API that provides machine readable descriptions of Google APIs that the client libraries take advantage of.
Today, we are announcing the Google APIs Discovery Service, which is the secret sauce behind the new client libraries. This service exposes machine readable metadata about Google APIs including:
- A directory of supported APIs.
- A "Discovery document" for each of the supported APIs that includes:
- A list of API resource schemas based on JSON Schema.
- A list of API methods and available parameters for each method.
- A list of available OAuth 2.0 scopes.
- Inline documentation of methods, parameters, and available parameter values.
You can use the APIs Discovery Service to build tools for interacting with Google APIs, such as IDE Plugins and client libraries. We use the service at Google to build a number of such tools:
- Google APIs client libraries - as described above
- Google APIs Explorer - an interactive web-based tool for exploring Google APIs
- Google API Support in Google Plugin for Eclipse - an IDE integration that allows you to import Google APIs support directly into your Eclipse project
Read more about Google APIs Discovery Service in the documentation, or explore its API in the APIs Explorer. If you are attending this year’s Google I/O and you want to know more about the service, make sure to attend our session “Building Custom Client Libraries for Google APIs” where you can chat with the developers of the service face-to-face.
We look forward to seeing what sorts of things you can build. Let us know of any issues and feature requests in our developer forum. Happy hacking!
Anton Lopyrev is an Associate Product Manager for Google APIs Infrastructure, previously a software engineer on Street View. He is a computer graphics enthusiast who is also passionate about product design.
Joe Gregorio is a Software Engineer. In the past four years at Google he’s worked on APIs, Google App Engine, Google Wave, and now has come full circle and is back working on APIs.
Monsur Hossain is a Software Engineer for Google APIs Infrastructure and enjoys making it easier to use APIs.
Posted by Scott Knaster, Editor
2013, By: Seo Master