Paginated results

Topic summary

Pagination of Shopify REST Admin API results was returning the same next-page token after the third page in Postman. The initial request used only updated_at_min, and subsequent calls incorrectly sent page_info and limit in headers.

Support advised to follow REST cursor-based pagination via the Link response header: include limit (<=250) in the first request, then use the Link-provided page_info and limit as URL query parameters for subsequent calls. Counting resources first can estimate the number of pages; the last page returns only a “prev” link.

Outcome: The original issue was resolved by moving pagination parameters out of headers and into the request parameters (page_info + limit), enabling proper page traversal.

New questions emerged: one user asked for a Qlik Sense looping example to fetch all orders; another asked how to obtain page_info in Postman; support clarified that page_info comes from the Link response header of the previous call and should be used in the next request.

Current status: Initial problem solved. Follow-up requests (code sample for Qlik Sense and practical parsing of page_info from the Link header) remain open without detailed, step-by-step parsing guidance.

Summarized with AI on December 25. AI used: gpt-5.

Hello again @awwdam ,

Thank you very much problem solved, I was sending the page_info in the request header instead of the body request. It’s working now!

Thank you !

1 Like