We are working on a new version of Etsy’s Open API and want feedback from developers like you.
gift_sender
as a new field to the following endpoints:
getShopReceipt
updateShopReceipt
getShopReceipts
createReceiptShipment
createShopShippingProfileUpgrade
and updateShopShippingProfileUpgrade
endpoints, the request fails if any shipping profile field or any of its entries were invalid. We've updated this to fail the request only if the upgrade being operated on is invalid.updateListing
, the shipping profile referenced by the shipping_profile_id
and all of its fields, along with its entries and upgrades, will now be validated. If the shipping profile is invalid then the request will fail until all the shipping profile validation errors are fixed.createShopShippingProfile
updateShopShippingProfile
createShopShippingProfileDestination
updateShopShippingProfileDestination
createShopShippingProfileUpgrade
updateShopShippingProfileUpgrade
updateListing
Here’s a list of the countries that will need a postal code in shipping profiles: https://developer.etsy.com/documentation/tutorials/fulfillment/#countries-requiring-postal-codes
deleteListingProperty
would fail if the listing had broken properties.updateListingProperty
in the case of broken properties to include exactly which properties in the listing are broken and need to be fixed.expected_ship_date
is emptygetShopReceipt
getShopReceipts
updateShopReceipt
ShopListing
state_timestamp
field as nullable. This field was incorrectly labeled as non-nullable.UserAddress
zip
field to nullable. This field was incorrectly labeled as non-nullable.To help protect shoppers’ privacy, we put some additional limits on the buyer info we share via the Etsy API. It only affects buyer_email
address field: most applications will not see this field returned in the responses of the endpoints anymore. Only in rare cases is this information included.
This change does not impact your API key’s ability to leverage the Etsy API. It will only affect if the buyer_email
address field is returned in the responses of the endpoints. If your application is not authorized to access this field, the endpoint will still return responses as normal, without this field being present in the response.
Bug Fixes:
ShopReceipt
payment_email
field to nullable.Addressed a bug in the documentation missing the “nulll” label for nullable fields. If your application generates models from the OAS schema, please regenerate them using the latest version.
ShopListing.getListing
to better explain why an error might be occurring. Now, in some scenarios a 422
will be returned with additional information as opposed to just a generic 500
error.