Notifications: ORDER_STATUS_CHANGE deprecated but ORDER_CHANGE causing 400 error

[dmequus]

Hi,

Just setting up our order notifications and noticed that Amazon have deprecated the ORDER_STATUS_CHANGE notificationtype.

I didn't see a problem until I tried to create a subscription for the ORDER_CHANGE notification type which causes a 400 error (unable to parse parameters).

Right now ORDER_STATUS_CHANGE is still working, but this will probably need to be addressed before Aug 31.

Thanks!

[dmequus]

I had a bit of time and can add a little more to this issue.

a) the Processing Directive is REQUIRED (first error you get if you leave it out) b) Once added, the error states it cannot parse the processingDirective for the notificationType ORDER_CHANGE.

I tried multiple combinations of adding or leaving out marketplaceId, aggregationSetting and eventFilterType to the processingDirective and can't get the magic answer, regardless of how the SP-API documentation states they are optional or not.

HTH

[SDP190]

Hi,

Same here, the current implementation there is no valid way to create "ORDER_CHANGE" notification subscription. trying to create it using the provided client api fails with an "cannot parse the processingDirective", when completely omitting the "processingDirective" it also failes.

[troliver]

Was anyone able to resolve this? I am having the same issue

[abuzuhri]

Still you get this error ? reopen if not solved