Changing the way Inventory and Shipping data is retrieved

[boly38]

Confirmation

• I confirm this post does NOT contain sensitive data for my account.

Question / discussion

Hi Etsy

2d ago, I received an mail about Etsy API change :

We are changing the way Inventory and Shipping data is retrieved. We will soon be removing support in endpoints getListing and getListingsByListingIds for returning this data through the ?includes parameters on these endpoints.
We will be releasing two new endpoints on July 15, 2026. These new endpoints are being introduced to our API to provide Inventory and Shipping data: 
- getListingsInventoryByListingIds
- getListingsShippingByListingIds

The Inventory and Shipping data itself is not changing—these new Inventory and Shipping endpoints return the same payloads currently available through these ?includes associations. The only change is that this data must be retrieved from the dedicated endpoints instead of being included in getListing and getListingsByListingIds responses.
This change impacts your application if you currently use either of the following parameters in these endpoints:
- ?includes=Inventory
- ?includes=Shipping

This is an advance notice only. On July 15, 2026, you'll receive a notification of the endpoints being publicly available for adoption. The adoption window will last until July 29, 2026. Beginning on July 29, 2026, requests that include ?includes=Inventory or ?includes=Shipping on the affected Listings endpoints will return a 400 Bad Request response. 

Hi Etsy Team,

I received the email notification regarding the upcoming Etsy API changes for Inventory and Shipping data.

(First, I apologize for posting this here, but I tried contacting support directly and haven't received a response yet.)

I have two questions/concerns regarding this announcement:

Typo in the date? The email mentions July 2026. Given the current date and how close this is, I wanted to double-check if this is indeed for July 2026 or if it was meant to be July 2027?

Adoption window is too short: If the timeline is indeed for this month, a 14-day window (July 15 to July 29) is extremely short for developers to update, test, and deploy code, especially during the summer holiday season. Is there any possibility to extend this deprecation deadline to give us more time to adapt?

Thank you for your help and understanding.

Best regards,

[boly38]

The deadline was July 29, and I only managed to complete the migration on July 30 — after 2 days of errors in production.
As a solo developer, I had to rush through the changes under pressure, debugging deployment issues caused by the tight turnaround.

That said, I'd like to reiterate my concern about the timeline.
Announcing a breaking change on July 15 with a hard cutoff on July 29 — giving developers only 14 days to adapt — during peak summer vacation season, is quite challenging.

Many solo developers and small teams simply cannot guarantee availability during this period.

For future breaking changes, I would strongly encourage the Etsy team to consider:
• A minimum 60-day adoption window, which is standard practice for public API deprecations
• Avoiding hard deadlines during major holiday periods (summer, end of year)
• Providing a sunset header or warning response before returning 400 Bad Request

Breaking changes requiring user action are part of API evolution, but the rollout timeline should reflect the reality of the developer community relying on your platform.

Thank you.