Release Notes for Shopping Content API
This topic describes recent changes made to Version 9.1 of the Content API.
October 1, 2020
This release includes the following changes:
- Added the Store resource. This resource lets you add and get stores in Microsoft Merchant Center. Read more. The resource is available to closed-beta participants only.
- Added the ProductStatuses resource. This resource lets you get the status of product offers in a store. Read more. The resource is available to closed-beta participants only.
August 13, 2019
This release includes the following changes:
- Updated the Products resource object to support the Netherlands market.
- Added nl (Dutch) as a possible value to contentLanguage
- Added NL (Netherlands) as a possible value to targetCountry
June 14, 2019
The following is a documentation-only change.
- Added the Request and method call limits topic, which suggests limits for HTTP requests and batch method calls.
November 9 2018
This release includes the following changes:
- Added the Inventory resource that you use to update a product's price and availability. The resource is available to closed pilot participants only. Read more.
August 1 2018
This release includes the following changes:
- Removed support for legacy credentials; you can no longer use username and password to access Content API. You must now use OAuth to access Content API. If you have not already done so, please migrate your account to use Microsoft accounts. For information, see We're changing the way you sign in. For details about using OAuth, see Get Started with the Content API.
July 2017
This release includes the following changes:
- Removed all references to version 9.0 from the document. Version 9.0 is no longer supported.
May 2017
This release includes the following changes:
The following Product fields are now required if the manufacturer assigns them.
If the manufacturer assigns values for these fields, you must specify them in your offer. If you do not, MMC will accept the offer for now but will return a warning message in the response (see warnings). You should update your code at your earliest convenience to begin providing this information.
If you do not specify the
brand
,gtin
, ormpn
fields, you must set the identifierExists field to false. Its default is true.Added the
warnings
field to the BatchItemError object.
March 2017
This release includes the following changes:
- Updated the documentation to reflect that your MMC store and catalogs are automatically enabled to use the Content API. You no longer have to use the Microsoft Advertising web application to enable your store and catalogs to use the API.
February 2017
This release includes the following changes:
- Updated the
Product
object's availability field to accept out of stock and preorder values. Only users in the pilot program may specify these values.
September 2016
This release includes the following changes:
- Added the promotionId field to the
Product
object. You use the promotion ID to associate a product offer with a promotion in your Promotions feed. - Updated the price and saleprice fields of the
Product
object to allow a minimum price of 0.0 (zero) under certain conditions. Previously, the minimum price allowed was 0.01 (1 cent).
December 2015
For information about the changes to the Content API services included in this release, see the following section.
Catalogs Management Resource
This release introduces the catalogs
resource.
For an overview and reference information about the catalogs
resource, see the topic Catalogs Management Resource. Code examples will be available in a forthcoming release.
October 2015
For information about the changes to the Content API services included in this release, see the following sections.
Status Resource
This release introduces the status
resource.
For an overview and reference information about the status
resource, see the topic Catalog Status Resource.
For an example of using the status
resource in code, see the topic Catalog Status Resource Code Examples.
Documentation Reorganization
The Content API was previously documented as "Version 1" and "Version 2". To make the documentation consistent, the version number used in documentation has been changed to use the version in the URI.
April 2015
For information about the changes to the Content API services included in this release, see the following sections.
Products Resource
The April 2015 release updated the products
resource to version 9.1.
Version 9 (previously version 1) of the products resource will be deprecated. Use version 9.1.
Version 9.1 of the Content API's products
resource was previously documented as version 2. Products Resource