Gorgias API error codes: what 401, 403, 409, 413 and 429 actually mean
When debugging a Gorgias integration, read the status code first. A 401 is an auth problem (check your API key or OAuth token); a 403 with working credentials means the connected app needs broader permissions; 409 usually means you raced another write or retried a create that already landed; 413 means shrink the request body; 429 means back off and honor the Retry-after header.
When debugging a Gorgias integration, read the status code first. A 401 is an auth problem (check your API key or OAuth token); a 403 with working credentials means the connected app needs broader permissions; 409 usually means you raced another write or retried a create that already landed; 413 means shrink the request body; 429 means back off and honor the Retry-after header.
Context: Gorgias documents specific error semantics: 401 means your credentials are wrong or missing, 403 means the credentials are valid but the app lacks permission for the resource, 409 signals a conflict with the current state of the resource, 413 means the payload is too large, and 429 means you hit the rate limit.
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.