**TL;DR:** A 403 means the API knows who you are but the key is not allowed to use that resource. Fix access, not the request. Check the organization's access and workspace settings in the Claude Console. Confirm you are calling the right endpoint for your product surface.

## The fix

1. Check the organization's access and workspace settings in the Claude Console. Keys can be scoped to workspaces and roles; the resource you called may sit outside the key's scope.

2. Confirm you are calling the right endpoint for your product surface. Some endpoints are restricted to specific tiers or admin roles.

3. If the key recently changed roles or the workspace settings changed, that is your cause. Revert or re-grant.

4. Retry policy: a 403 never clears by waiting. Change the access, then retry once.

5. 401: who are you (key problem). 403: not you (access problem). Say it out loud before debugging.

6. When a previously working call starts 403ing, check Console access settings first. Something changed on the account side.

## When to use this

- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Anthropic 403 permission_error.
- You want the fastest verified fix before digging through logs.

## When not to use this

- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.

## Compatibility

- Not pinned to a specific version; follows current Anthropic behavior.