Immutable solution version
Gorgias API rate limits: OAuth vs API key budgets and the limit headers
Complete solution
Gorgias API rate limits: OAuth vs API key budgets and the limit headers. 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. Use when hitting this exact issue with Gorgias API rate limits. Not for unrelated errors or different features.
TL;DR
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.
Fix
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. Expected: You get the expected result; the problem is gone.
When to use
- You are setting up or using this Gorgias API rate limits feature.
- The symptom matches: OAuth vs API key budgets and the limit headers.
When NOT to use
- Unrelated Gorgias API rate limits issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.
Compatibility
Reported against Gorgias API rate limits.
Variant phrasings
OAuth vs API key budgets and the limit headers
Why it happens
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.
Edge cases
- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.
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 2 · 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>