Just getting started with the Taxonomy API? See the following documents for details on using this API:
The following table lists the releases for the Taxonomy API:
Version | Release Date | Summary of Release |
---|---|---|
Version 1.1.1 | 2025-05-07 | Adds a new aspectConstraint field, aspectAdvancedDataType, to the fetchItemAspects and getItemAspectsForCategory responses. |
Version 1.1.0 | 2024-08-26 | Added a new method, getExpiredCategories, that retrieves mappings of expired leaf categories to corresponding active leaf categories. |
Version 1.0.1 | 2023-04-04 | A backslash (\) may now be inserted immediately prior to an embedded comma within a filter value when calling getCompatibilityPropertyValues. This will prevent the comma from being interpreted as a delimiter between successive property name/value pairs. |
Version 1.0.0 | 2020-10-15 | The initial version of the GA version of Taxonomy API |
Version 1.1.1
As part of EU's Common Charger Directive (CCD), sellers in the EU and Northern Ireland listing certain rechargeable devices (such as portable electronic devices) are expected to indicate the power range of the charger (if a charger is provided with the product). This information is provided using the new Device Charging Range aspect when creating or revising a product listing.
In order to support this new aspect, a new aspectConstraint field, aspectAdvancedDataType, was added to the fetchItemAspects and getItemAspectsForCategory responses. This field indicates any additional data type requirements for an aspect value, with the first use case being the Device Charging Range aspect. For more information about specifying the Device Charging Range aspect and other aspects related to CCD, see the Common Charger Directive topic in our Selling Integration Guide.
Version 1.1.0
This release adds a new method, getExpiredCategories, to the category_tree resource. This method retrieves the mappings of expired leaf categories in the specified category tree to their corresponding active leaf categories.
Version 1.0.1
When filtering values returned from a getCompatibilityPropertyValues call, commas are used as delimiters between successive name/value pairs. Previously, when a value included a comma (e.g., BodyStyle:AWD B9 8W5,C8WD
) the comma would be interpreted as a delimiter. Beginning with this release, a backslash (\) may now be inserted immediately before a comma (e.g., BodyStyle:AWD B9 8W5\,C8WD
) to prevent it from being evaluated as a delimiter.
Version 1.0.0
This is the initial release of the General Availability (GA) version of Taxonomy API. For a list of the calls, see the Taxonomy API Reference.