Configuration API - new pagination fails for restaurantServices endpoint
CompletedThe call to restaruantServices without the deprecated pageSize returns error code 400 (Bad Request.

It works without the error when adding pageSize=10 which will be deprecated on 12/6:

All other requests work with the new pagination. Is there something that I need to do differently? Or is this a bug that needs to be fixed prior to 12/6?
-
Official comment
Hi Susann Hoehnelt,
I'm happy to report that this issue has been fixed and token-based pagination now works in the restaurantServices endpoint of the configuration API. Thanks again for reporting the problem and let us know if you have additional questions.
-
Hi Susann,
Thanks for bringing this to our attention! I'll notify our engineering team and will let you know what I hear.
I just tested a few config API requests and can reproduce this error in the /restaurantServices endpoint. I did not encounter this error on other configuration API endpoints when I omitted the pageSize parameter, only /restaurantServices. That said, we'll test all endpoints to be sure and will investigate what's going on with /restaurantServices.
0 -
Hi Susann,
Just want to keep you posted that our engineering team is working on a fix for this issue. I'll post here after the fix is released. Thanks for bringing the issue to our attention.
0
Please sign in to leave a comment.
Comments
3 comments