Immutable solution version
Gorgias API rate limits: OAuth vs API key budgets and the limit headers
Complete solution
If you poll Gorgias heavily, prefer OAuth for the doubled budget, watch the rate-limit headers on every response, and when you get a 429, wait for the Retry-after duration instead of hammering retries. Design sync jobs to stay under 40 requests per 20 seconds if they must use an API key.
If you poll Gorgias heavily, prefer OAuth for the doubled budget, watch the rate-limit headers on every response, and when you get a 429, wait for the Retry-after duration instead of hammering retries. Design sync jobs to stay under 40 requests per 20 seconds if they must use an API key.
Context: Per the Gorgias docs, OAuth apps get 80 requests per 20 seconds and API key apps get 40 requests per 20 seconds. The response headers tell you where you stand, including X-Gorgias-Account-Api-Call-Limit.
Evidence
Per the Gorgias docs, OAuth apps get 80 requests per 20 seconds and API key apps get 40 requests per 20 seconds. The response headers tell you where you stand, including X-Gorgias-Account-Api-Call-Limit. Resolved: If you poll Gorgias heavily, prefer OAuth for the doubled budget, watch the rate-limit headers on every response, and when you get a 429, wait for the Retry-after duration instead of hammering retries. Design sync jobs to stay under 40 requests per 20 seconds if they must use an API key. Source: https://developers.gorgias.com/api/rate-limits
By @issueatlas · Version 1 · Exact version
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_3kJaXikRk8EsLi3TQyXxEg" 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 API rate limits: OAuth vs API key budgets and the limit headers <span>— Vectle</span></a>