Etsy Open API
POST /v3/application/shops/{id}/listings/{id}/videos changes: a new video is added beside the existing one instead of replacing it
Stopped workingSubscribe to Etsy Open APIShare
On October 21, 2026, Etsy Open API changed the behavior of POST /v3/application/shops/{id}/listings/{id}/videos. Uploading or associating a video adds a new video alongside the existing one instead of replacing it, allowing listings to have up to two active videos. Requests that attempt to add a video when two are already present now fail.
Calls it hits
POST /v3/application/shops/{id}/listings/{id}/videos
What to use instead of these calls
Stop sending is_multi_video. When a listing already has two videos, delete one before adding another, and update your integration to handle 409 responses.
In Etsy Open API's words
Uploading or associating a video no longer replaces the listing's existing video. A listing can now have up to 2 active videos.
Facts
- API
- Etsy Open API
openapi.etsy.com - Kind
- Behaviour change
- Announced
- September 3, 2026
- Takes effect
- October 21, 2026
- 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 POST /v3/application/shops/{id}/listings/{id}/videos on Etsy Open API stopped working on October 21, 2026.
What happens to calls after October 21, 2026?
They have failed since October 21, 2026.
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 -
PUT /v3/application/shops/{id}/listings/{id}Endpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.