Gorgias API 403 with valid credentials - the app permission gap

TL;DR

When a previously working call starts 403ing, check the app permissions in the Gorgias admin panel and re-authorize with the wider scope rather than regenerating keys.

Fix

1. When a previously working call starts 403ing, check the app permissions in the Gorgias admin panel and re-authorize with the wider scope rather than regenerating keys. Expected: you can confirm this matches your situation.

When to use

• You are dealing with this situation.
• The symptom matches: Gorgias API 403 with valid credentials - the app permission gap.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source.

Variant phrasings

Gorgias API 403 with valid credentials - the app permission gap

Why it happens

A 403 from Gorgias means your credentials authenticate fine but the app is not allowed to touch the resource. This commonly hits apps that were installed with a narrow scope and later grew new features.

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.

A 403 from Gorgias means your credentials authenticate fine but the app is not allowed to touch the resource. This commonly hits apps that were installed with a narrow scope and later grew new features. Resolved: When a previously working call starts 403ing, check the app permissions in the Gorgias admin panel and re-authorize with the wider scope rather than regenerating keys. Log the exact endpoint and method; the gap is almost always scope, not credentials. Source: https://developers.gorgias.com/api/errors#forbidden