API 3.0 "readiness_state_id" key consistently failing when READING the catalog

[DecoPro]

The issue was reported to be resolved but it has not been (see https://github.com/etsy/open-api/discussions/1418).

My app uses API 3.0 to retrieve and publish listings. It downloads data from the catalog and fails on that error on seemingly random listings. It retrieves a significant number then fails on that error. I have had to Deactivate the "faulty?" listings to get past them but every subsequent run fails on another one. I ran the app 3 consecutive times (without deactivating an offending listing), and observed it failed on different listings each time. I checked the logs and found that the previous failure listings were not included in the subsequent runs. It appears that the API returns ALMOST consistent results with just enough variance to make the contents of the returned data set unpredictable.

As a result, we are unable to mange existing nor publish new listings - this has been happening since 16 June 2025. The most recent previous date of execution of our app was 7 May 2025, when it was successful. Posts on discussion boards make it clear that the API was altered to "roll back" the "readiness_state_id" key after which all hell broke loose.

Why would reading from the catalog via the API fail on that key rather than ignoring such an error and moving on?

I cannot report whether or not this error occurs when writing to the catalog because my app never gets to that point. It fails as soon as one exception is thrown.

My app was written by a 3rd party. He is no longer able to maintain it. It retrieves listings data from Etsy, reads an XLS file with new listings and updates then uses the appropriate API calls to add to or update the catalog. I have the source code, but do not have the in-house expertise to take over its maintenance. I am not fixed on Kotlin/Java, but it would likely be more efficient to update the current code than to start from scratch, but YMMV. I would also like to expand its functionality to upload more than 1 image - up to 6 images and (if possible) up to 2 videos is ideal. I am open to suggestions for (re)development but I will not be able to sell a recurring subscription to C-level management.

This error is costing us a fortune in lost sales. Etsy is our most active market behind AMZ; we are a Star Seller. Losing the ability to add or update listings is devastating. This must be fixed ASAP.

[ArtDollsbyJD]

Etsy is not here in the forums.  You will need to contact Etsy to talk about this.

Contact us under Help or use Chat but expect to be referred to a specialist.

Etsy has never been one to support bringing in listings from other venues.  If you are having issues with an app they don't partner with you will need to contact the support team of that app.  If they did support, you will need to ask Etsy if they will continue as you say the person involved is not managing it any longer.  I see from the discussion that they said it was but someone said it wasn't.  That doesn't surprise me.

But overall contact Etsy using Contact us.

[DecoPro]

Thank you for your reply. I have reached out to Etsy via E-Mail, the Phone Request page, and the Contact Us page, but they have not responded. This is 11 days now of silence.

Please allow me to correct your misunderstanding about my app. I am not attempting to import listings from another marketplace. I have an in-house developed system that manages product data and exports the information required by various marketplaces. Through it, I am able to generate original listing data for 7 markets. It used to be 8, but I can no longer publish to Etsy because of this API error.

Also, the app I am using to publish to Etsy was developed by a 3rd party we hired for the purpose. He is no longer able to support the app (the reason is personal and irrelevant) so we cannot apply a workaround. This issue was caused by Etsy and should be corrected by Etsy.