Google improved content API for shopping

Google presented the Content API for shopping few years ago in order to help the advertisers oversee and update the Google Merchant Center product data automatically and at scale. In June, Google announced another version of this API, providing more knowledge into your data quality as well as new options in order to help you keep your data fresh and to make adwords management much at ease.

The existing shopping Application Programming Interfaces (API) has two principle parts such as

Content API for Shopping

Search API for Shopping

 

The Base API was replaced with these two Shopping APIs. Content API made it simpler and speedier to transfer product information to Google. Advertisers were able to utilize the Content API to transfer their information and make incremental updates to recurrently changing features like price and accessibility. Marketplaces and Aggregators were likewise able to utilize the new Content API to manage multiple client accounts. The Search API streamlined access to product information and optimized to display the most relevant product results.

Now as the new key functions of API were announced, data quality, inventory and account management are the features promoted by Google primarily. In this version of API, you can request for full data quality reporting for the entire account and in addition for item level data which turned out to be disapproved, as a result of inaccurate prices or inaccessible landing pages. The inventory service gives you a chance to update the price and availability of any product while refraining from resubmitting other product details within adwords management. All account types are also enabled with present account management features such as linking Adwords accounts, including authorized users and updating settings.

Customer libraries and better tooling are another option permitted with this version of API. A much broader choice of programming languages and data formats are supported such as client libraries for .NET, Dart, Go, Java, JavaScript, Objective-C, PHP, Python and Ruby in case you would prefer not to parse JSON or XML yourself. OAuth 2.0 authorization is used by these libraries while working with the content API and Google APIs such as the API console in order to make your adwords management more comfortable.

Likewise, another feature supported in version 2 is simplified message formats. The new XML format is much lighter than in version 1 of the API.JSON, which is less difficult to work with and also utilizes fewer bytes to transfer the same information.

Google announced that the API version 1 would only be available until the end of February 2015 and adopting to the version 2 of the API would be convenient as Adwords users will be able to experience better advantages of Google’s newly introduced features from this moment. Therefore, it is better to start experimenting it now than later before it can be too late to mingle.