Gorgias removed offset pagination; list endpoints are cursor-based now

Never send offset or page to a Gorgias list endpoint. Start with GET https://YOURSUBDOMAIN.gorgias.com/api/tickets?limit=100 and read meta.nextcursor from the response. Loop: request with cursor=nextcursor, extend your results, stop when nextcursor is null. On 429 mid-loop, honor Retry-after and resume from the last cursor, since cursors are stateless. If you maintain an old extractor that still sends offset, expect it to return page one forever; rewrite it to the cursor loop.

Context: Web (ClonePartner export guide, real migration problem): reports that Gorgias removed offset-based pagination in February 2024. Every list endpoint is cursor-based now. Responses include nextcursor and prevcursor fields, and most endpoints cap limit at 100. Old code passing offset/page params silently returns the wrong data set, not an error. The page gives the working pattern: keep following next_cursor until it returns null.

Source: Web (ClonePartner export guide, real migration problem): reports that Gorgias removed offset-based pagination in February 2024. Every list endpoint is cursor-based now. Responses include nextcursor and prevcursor fields, and most endpoints cap limit at 100. Old code passing offset/page params silently returns the wrong data set, not an error. The page gives the working pattern: keep following next_cursor until it returns null.

Verified resolution: Never send offset or page to a Gorgias list endpoint. Start with GET https://YOURSUBDOMAIN.gorgias.com/api/tickets?limit=100 and read meta.nextcursor from the response. Loop: request with cursor=nextcursor, extend your results, stop when nextcursor is null. On 429 mid-loop, honor Retry-after and resume from the last cursor, since cursors are stateless. If you maintain an old extractor that still sends offset, expect it to return page one forever; rewrite it to the cursor loop.

Source URL: https://clonepartner.com/blog/how-to-export-data-from-gorgias-methods-api-limits-formats