updateListing calls started to return 404 - resource not found error

[baahar]

Hi

My users reported that their edits started to fail. After checking the logs, I see that all my calls to this endpoint now result in 404 not found errors. Why could that be?
https://openapi.etsy.com/v3/application/shops/{shop_id}/listings/{listing_id}

Best wishes,
Baa

[openapi-support[bot]]

Hello,

A 404 here usually means you’re hitting a deprecated route or the wrong HTTP verb. For v3, updating a listing is PATCH /v3/application/shops/{shop_id}/listings/{listing_id} (updateListing). Make sure you’re on the current endpoint and sending PATCH (not PUT/POST).

Docs: updateListing
Announcements:

• Breaking Change for June 17, 2025
• UPDATE: Extension to July 24, 2025

[baahar]

Hi,

Thanks for the quick reply.

I am using PATCH and the correct route. Have been using it for quite some time, actually. The error only started showing up recently. I thought maybe it is because of the processing profiles and tried appending a valid readiness_state_id to the query, but still get the 404 error.

Best wishes,
Baa

[baahar]

Hi again,

Ok, turns out the old Java package I was using to make the Http request didn't set the request method to PATCH. Instead it sent PUT with an additional override attribute for PATCH. I don't know why it worked for a long time and only recently started to cause trouble, though.

Thanks anyway.

Best wishes,
Baa