Breaking Change for April 15, 2025 #1378
Replies: 2 comments
|
Has this update been postponed? I am still receiving successful responses from the API. |
0 replies
|
Hi, You state that /getPropertiesByTaxonomyId will no longer return deprecated properties for a given seller taxonomy_id. But for taxonomy_id = 1764, for instance, I am still getting many properties from the list above. Could you please clarify? Best wishes, |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
We’re getting in touch to let you know about the deprecation of some listing property values that will affect Etsy’s Open API. Starting April 15, 2025, Etsy will no longer accept references to the property_ids of deprecated properties in requests to get, create or update a property or listing. We’re doing this to ensure that the Open API is in line with the Etsy web experience.
What are Variations and Properties?
Variations are a means to offer different options for an item within the same listing. For example, if a seller sells a dress with different sizes and colors, they can specify these options in that dress listing’s variations.
Properties describe the ways in which a listing may vary (and therefore may use a variation). Examples of valid properties include "Sleeve length" and "Primary Color".
What's changing?
Starting April 15, 2025, in order to provide a better experience to buyers viewing listings with variations, we will deprecate certain properties, and reduce support for using those deprecated properties in variations. Any existing listings with variations that are linked to the deprecated properties will be converted to a custom variation so that those listings may remain available for sale on Etsy. That migration will be complete by Apr 15, 2025. If you have cached any property_ids , we recommend that you call getListingProperties to get the new property_ids for any listings formerly connected to variations with deprecated properties after the migration.
Affected endpoints:
Deprecated Properties
Update your app
If you have stored any references to the property_ids of deprecated properties, those should be removed, and you should be sure to retrieve the most up-to-date property_ids available at the time of your request using the getListingProperties endpoint until the full migration is complete.
All reactions