You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
https://sellingpartnerapi-fe.amazon.com/orders/v0/orders?LastUpdatedAfter=2023-08-18T00:00:00+09:00&OrderStatuses=Unshipped,PartiallyShipped&MarketplaceIds=1VC38T7YXB528&FulfillmentChannels=MFNwould result in the following error.
> JSON.parse(response.body)
=> errors"=>[{"code"=>"InvalidInput", "message"=>"This is invalid input", "details"=>"Invalid date/time field [lastUpdatedAfter]"}]}]
+09:00 is removed and the response is returned normally. Why is this?
It appears that LastUpdatedAfter must be UTC time.
Therefore, the JTC notation seems to have resulted in an error.
I would like the documentation to clearly state that the time is in UTC.
Hey @asagawa0519 , shouldn't this be the case(specifying time to be in UTC) for LastUpdatedBefore, ChangedAfter, ChangedBefore or all the other date-time format params?
Also I have created a pull request #335 for only LastUpdatedAfter. Please review.
And if changes have to be made in documentation/description of other date-time params , please let me know.
This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.
https://sellingpartnerapi-fe.amazon.com/orders/v0/orders?LastUpdatedAfter=2023-08-18T00:00:00+09:00&OrderStatuses=Unshipped,PartiallyShipped&MarketplaceIds=1VC38T7YXB528&FulfillmentChannels=MFN
would result in the following error.+09:00 is removed and the response is returned normally. Why is this?
If it succeeds
https://sellingpartnerapi-fe.amazon.com/orders/v0/orders?LastUpdatedAfter=2023-08-18T00:00:00&OrderStatuses=Unshipped,. PartiallyShipped&MarketplaceIds=A1VC38T7YXB528&FulfillmentChannels=MFN
The text was updated successfully, but these errors were encountered: