[BUG] 400 Bad Request when using NextToken on GetOrders

[BasilAlhakami-SonaEnterprises]

I receive a 400 Bad Request response, when calling the /orders/v0/orders endpoint. when I have the NextToken in the request I submitted a case# 8390283141

this thread: https://github.com/amzn/selling-partner-api-models/issues/384

is discussing the same issue but with https://github.com/amzn/selling-partner-api-models/issues/384

the bug was resolved by @parvathm for the financialEventGroups API

I wonder if the same fix should apply to Orders

Thanks

[ShivikaK]

Hello @BasilAlhakami-SonaEnterprises

Thank you for raising this issue and providing the case ID.

The case is being reviewed by the Support team and additional details will be provided via the case.

Please continue monitoring the case for further updates.

Thanks, Shivika Khare Selling Partner API Developer Support

[RamprasadAkella]

@ShivikaK Can you please let us know what's the latest update on this ? We are also seeing the same issue on our side.

[BasilAlhakami-SonaEnterprises]

@RamprasadAkella the problem was that the token has '/' in the string so including it in the url breaks it. you need to url encode the token and that worked for me

[fernadodemitropulos]

the problem still exists, this thread should not be closed

[flagile]

this problem for order api is still existing, could you pls have to fix? thank you very much @ShivikaK [ShivikaK(https://github.com/ShivikaK)

[matijaskorup1991]

the problem is still here, why is this closed?

[kensplanet]

Problem exists

[ImportFence]

the problem is still here, why is this closed?

Did you try to only use the nextToken parameter and keep the other three parameters be unchecked while you are trying to fetch 2+ pages data?