You can now paginate through Items and Variations with cursor-based pagination for more reliable, scalable listing - especially for large catalogs.

What’s new

• GET /v2/items and GET /v2/variations now support cursor-based pagination via next_page_cursor.
• Each response may return next_page_cursor; pass it in the next request to fetch the next page of results.

Why it matters

• More reliable pagination for large result sets (reduces offset-related gaps/duplication).
• Easier to build long-running or resumable export/audit workflows.

Common customer use cases

• Catalog audits / backfills: Iterate through the full catalog safely, without relying on offset math.
• Resumable scripts: Store the last cursor to resume processing after interruptions.
• Large-catalog integrations: Reduce risk of missed/duplicated entities when the underlying catalog is changing.

How to use it (high level)

• Make a request and read next_page_cursor from the response.
• Repeat requests with next_page_cursor until it’s empty/omitted.

Notes

• next_page_cursor can’t be combined with page or offset.
• When using cursor pagination, total_count is omitted.

Learn more about Retrieving Items