JSON_LISTING_FEED - Inaccurate submission results?

[AitorUria]

Hello everyone,

While test the JSON_LISTING_FEED we have encountered an error by which this method does not accurately return the "Records successful/submitted" whenever an error is encountered and excludes all error messages.

As a test, we have attempted to create a listing for an ISBN not authorised on Amazon UK.

While previous the flat file method returns the error:

"9785856461731-1 8056 Error The SKU [ 9785856461731-1] was submitted with incorrect ASIN provided as the "external product ID". Please resubmit your product with correct ASIN or resubmit your product with a product identifier other than the ASIN (e.g., UPC, ISBN, etc.). You can find information on other product identifiers on: https://sellercentral.amazon.co.uk/gp/help/200211450."

The JSON method returns as a submission result:

{"header":{"sellerId":"XXXXXXXXX","version":"2.0","feedId":"1200349020097"},"issues":[],"summary":{"errors":0,"warnings":0,"messagesProcessed":1,"messagesAccepted":1,"messagesInvalid":0}}

Is this a bug or are we missing something? Access to full responses allows developers to analyze performance metrics such as response times and payload sizes, enabling them to optimize their applications accordingly.

Any feedback would be greatly appreciated.

[jawheral]

Hi @AitorUria,

The Listings API or the JSON_LISTINGS_FEED are not synchronous APIs. They will only return schema validation issues, many other validations are run post-submission and added on the listing, i.e the submission is accepted but validations are still being run in the background. To retrieve the actual issues, you either use the getListingsItem operation while adding issues in the includedData parameter or subscribe the LISTINGS_ITEM_ISSUES_CHANGE notification to receive your listings issues as they are added.

Best,
Jawher
Selling Partner Developer Services

[AitorUria]

Thanks @jawheral we will take this road and enquire further if necessary.

Kind regards

[StaniBanani]

I mean that hole thing is more then deprecatet. I tryed it today. I followed all the steps of the Amazon Tutorial for Java. Most of the Java code throws exceptions as hell. I thinked about to fix the code. But at least they changed some stuff about the SP-API. So just creat your own code. Works much smoother and faster as fixing this old ham here.