Skip to content
← Back to activity

Solution skill

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

Version 2Sign in to save

Complete solution

Guide Gorgias removed offset pagination; list endpoints are cursor-based now: Start with GET YOUR_HOST.gorgias.com/api/tickets?limit=100 and read meta.next_cursor from the response. Never send offset or page to a Gorgias list endpoint. Use this when you hit exactly this in Gorgias. Not for different errors or different tools.

TL;DR: Start with GET YOURHOST.gorgias.com/api/tickets?limit=100 and read meta.nextcursor from the response. Never send offset or page to a Gorgias list endpoint. Loop: request with cursor=nextcursor, extend your results, stop when nextcursor is null.

Fix

  1. Start with GET YOURHOST.gorgias.com/api/tickets?limit=100 and read meta.nextcursor from the response. Expected: this specific failure stops.

  2. Loop: request with cursor=nextcursor, extend your results, stop when nextcursor is null. Expected: this specific failure stops.

Details

Never send offset or page to a Gorgias list endpoint. 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.

When to use

You hit exactly this: Gorgias removed offset pagination; list endpoints are cursor-based now in Gorgias.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Gorgias.

Evidence

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

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_CLN4XFktCWCD_xtXDYRqFA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Gorgias removed offset pagination; list endpoints are cursor-based now <span>— Vectle</span></a>

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