API V2 - Orders endpoint not returning next_page_token

API Q&A
1

There is a bug with the v2 orders endpoint, it is not returning the next page token, so we can’t get the next page.

2

Hi @Nick_Kulavic,

Thanks for reporting this. We’re aware of the issue and the team is currently looking into it. It’s listed in our known issues tracker.

3

Omar,

The status says “In Progress”, and the Date shows 10/4/2026.

Is this accurate? This was reported years ago and is a major blocker for us, especially since some of the ecommerce tables are not directly accessible.

If this is a real date, can we get it expedited and corrected this week???

Again, it is a major blocker.

Respectfully,

~Christian

Orders GET Defect Returning incomplete list and no page_token_id In Progress 10/4/2026
4

Hi @Christian_WIles,

Thanks for flagging this, I’ve corrected the date in the tracker. The correct date is 4/10/2026.

We now have a solution in place that is currently being tested, so it should be released soon. I’ll let you know as soon as it’s deployed.

Appreciate your patience while we get this resolved.

Best,
Omar

5

Hi @Nick_Kulavic, @Christian_Wiles and @Casey_page,

Just wanted to share an update that this issue has now been resolved. The fix has been implemented and the endpoint is returning the pagination token as expected.

Thank you all for your patience while we worked through this!

Best,
Omar