Etsy Open API
PUT /v3/application/shops/{id}/listings/{id} endpoint removal
Stopped workingSubscribe to Etsy Open APIShare
Calls to PUT /v3/application/shops/{id}/listings/{id} on Etsy Open API stopped working on July 24, 2025.
Calls it hits
PUT /v3/application/shops/{id}/listings/{id}
What to use instead of these calls
Call updateListing with PATCH /v3/application/shops/{shop_id}/listings/{listing_id} instead.
In Etsy Open API's words
Starting July 24, 2025 all requests to these endpoints will return a 301 Moved Permanently response code with additional information in the request header and body pointing to the current, corresponding endpoint.
Facts
- API
- Etsy Open API
openapi.etsy.com - Kind
- Endpoint removal
- Announced
- April 17, 2025
- Takes effect
- July 24, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Etsy Open API's own pages
Questions
When does this change take effect?
Calls to PUT /v3/application/shops/{id}/listings/{id} on Etsy Open API stopped working on July 24, 2025.
What happens to calls after July 24, 2025?
They have failed since July 24, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Etsy Open API 4
-
/v2/*Version retirement Stopped working -
GET /v3/application/shops/{id}/listings/{id}/imagesEndpoint removal Stopped working -
GET /v3/application/shops/{id}/listings/{id}/images/{id}Endpoint removal Stopped working -
POST /v3/application/shops/{id}/listings/{id}/videosBehaviour change Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.