catalog APIv1_beta.2.0

Beta Catalog API release notes

Just getting started with the Catalog API? See the following documents for details on using this API:

The API release history

The following table lists the beta releases for the Catalog API:

Version

Release Date

Summary of Release

Version 1_beta.3.1

2019-07-11

Three change request methods deprecated

Version 1_beta.3.0

2018-07-31

New fields returned in Product Metadata methods

Version 1_beta.2.0

2018-05-24

Two new methods were added to the API

Version 1_beta.1.0

2018-04-15

Three new methods were added to the API

Version 1_beta.0.0

2018-02-15

Initial release of Version 1_beta.0.0

Version 1_beta.3.1

The three catalog change request methods in the Catalog API are deprecated, and are scheduled to be decommissioned in Q1 of 2020. Below is the expected behavior if a user attempts to use any of these calls:

  • getChangeRequest: Currently, this method may still return data for a valid change request ID, but the data will be static, the status will not change, and it will not be possible to make any changes to the change request. At any time, it is possible that all catalog change requests for a user will be removed, and then this method will just trigger this error: The specified change request ID was not found. (error code 75150).
  • getChangeRequests: Currently, this method may still return existing change requests for a user, but the data will be static, the statuses will not change, and it will not be possible to make any changes to any of the change requests. At any time, it is possible that all catalog change requests for a user will be removed, and then this method will just return an empty changeRequests array.
  • createChangeRequest: This method is no longer supported for any eBay categories and will return this error if used: Change Request is not supported for this product at this moment. (error code 75157)

Version 1_beta.3.0

The getProductMetadata and getProductMetadataForCategories calls were updated to return the following new metadata:

  • GTIN fields (ean, isbn, and upc): constraint container will indicate whether the GTIN type is required or not, and if known/applicable, actual GTIN values will be returned under the valueAssociatedWithProduct and/or values fields.
  • importance field will be returned under the constraint container for both product aspects and identfiers to indicate the importance of providing that aspect/identifier in a catalog product record. The ImportanceEnum type was added to define the importance values.

Note: The getProductMetadata and getProductMetadataForCategories calls are currently supported in the eBay Sandbox and Production environments for testing purposes. For more information, see Testing Product-Based Shopping Experience APIs in sandbox and Testing Product-Based Shopping Experience APIs in production.

Version 1_beta.2.0

To provide sellers with aspect information they can use to better define their change requests for the eBay catalog, the following two calls were added to the Catalog API:

Note: These calls are currently supported in the eBay Sandbox and Production environments for testing purposes. For more information, see Testing Product-Based Shopping Experience APIs in sandbox and Testing Product-Based Shopping Experience APIs in production.

Version 1_beta.1.0

To support the ability of sellers to submit feedback and request changes and improvements to the eBay catalog, the following three calls were added to the Catalog API:

Note: These calls are currently supported in the eBay Sandbox and Production environments for testing purposes. For more information, see Testing Product-Based Shopping Experience APIs in sandbox and Testing Product-Based Shopping Experience APIs in production.

Version 1_beta.0.0

This is the initial release of the Catalog API, Version 1_beta.0.0. For a list of the new calls, see the Catalog API Reference.