Ah, good catch @Dmarcotrigiano! The link should actually be https://developers.etsy.com/documentation/reference (developers with an s at the end). We’ll update that redirect so it works as expected. I’ll reply here when that’s fixed, but the link I provided should work fine.

What stage is the API in? Your general release is scheduled to be within Q3 which begins in 15 days, but the API appears to be mostly access controlled. My client and I are waiting to hear back from [email protected] for about a month now, with 5 emails sent pertaining to access for the Open API v3. Please provide us with an update so that we may carry on with our responsibilities.

Link to Documentation Issue https://developer.etsy.com/documentation/reference

What would you like to change? Something went wrong... Error downloading https://www.etsy.com/openapi/generated/oas/3.0.0.json Failed to fetch Stack trace

ReDoc Version: 2.0.0-rc.48 Commit: 7b78e75

Why are you proposing this change? I cannot see the documentation for the API on the website.

Removed the oas json file that is in the repo. Replace it with the link to the generated oas in the Readme

This is definitely something that should have been added. It's deeply frustrating that with so many sellers seeking analytics tools, we as developers can't provide a solution using just the Etsy API.

Oh interesting I need to sign all the commits. Would the best choice just be to blow up this branch and create a new one?

Removed the oas json file that is in the repo. Replace it with the link to the generated oas in the Readme

Would be great if we could add a parameter to specify a country so that the results roughly resemble what people in other countries see. For example, a parameter like country=DE that would only show results that are available to German shoppers.

Describe the bug The count value is limited to 50,100.

To Reproduce Run query in v2 API for a keyword like https://openapi.etsy.com/v2/listings/active?api_key=API_KEY_GOES_HERE&keywords=gift

Expected behavior A count value that is similar to what can be seen on the website. In the "gift" example, the expected count would be around 25.6M

Screenshots n/a

Additional context n/a

Thanks for fixing, now works as expected in v3 API.

Current Endpoint Design It would be good to know where the shop is based. eg. US, UK, DE, etc

Proposed Endpoint Design Change Add country to the response.

Why are you proposing this change? For comparing shops that a local and abroad. Some of our customers have expressed difficulty in competing with other shops on price point. If we can help them understanding the location of other shops, we can help them with pricing their products. While this info is easy to gather from the public site, it would be great to expose in the API too (save our customers a few clicks) and gives us the ability to do a lot more for sellers.

I see shop_location_country_iso and its working nicely, thanks guys.

Can we possibly get some (rough) timeframes on when all v3 methods will be fully production ready and when v2 is slated to be deprecated? We need to plan development resource to handle this change so any dates you could share with us would be much appreciated.

Current Endpoint Design Current design does not include the item SKU nor the variations nor the personalisation added by the customer during checkout

Proposed Endpoint Design Change Please add the SKU, variations and personalisation

Why are you proposing this change? SKU/variations: required to identify the right item personalisation: To process the customer wish within our system

This would be very useful for us too.

Current Endpoint Design

1. The ShopTransaction object in the response does not contain information like "digital_file_download_status", which represents the fulfillment status of digital orders.
2. The endpoint name getShopReceiptTransaction is a little confusing because the functionality is about querying ShopTransactions, nothing relevant to Receipt. Better remove "Receipt" from endpoint name.

Proposed Endpoint Design Change

1. In ShopTransaction object, add "digital_file_download_status" field (or collection if there are multiple digital items) to show the file download status, i.e. "Not Downloaded", "Fully Downloaded" or "Partially Downloaded".
2. Remove "Receipt" from endpoint name in the documentation.

Why are you proposing this change? The reason for proposing to add "download status" is to allow external applications to find those "paid but not downloaded" digital file orders, and send alerts/reminders to the shop owner or customer.