Pricing
Claude Code "API Error: 403": Request Not Allowed and Access Grant Fixes
Claude Code says "API Error: 403" with "Request not allowed" or "requires an access grant"? Which 403 you have, what causes it, and the fixes that work.
9 min read
Error strings quoted from Claude Code GitHub issues #50411, #99837, #51610, #49885 and #94044 (verified Nov 4, 2026, re-checked Nov 5, 2026). Causes and fixes checked Nov 5, 2026 in Claude Code’s install troubleshooting page, its error reference and Anthropic’s API error docs. Every source is listed at the bottom. No affiliate links on this page (how we work).
The exact errors: API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}
The classic one, from #50411 (verified Nov 4, 2026):
Please run /login · API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}} /login Login OAuth error: Request failed with status code 403The second is the newer one people are hitting, from #99837 (opened Oct 6, 2026, verified Nov 4, 2026):
Please run /login · API Error: 403 Access to this model requires an access grant your request does not have.And a close cousin from #51610 (verified Nov 4, 2026):
Please run /login · API Error: 403 {"type":"error","error":{"type":"permission_error","message":"Permission denied"},"request_id":"req_…"}The one-line answer: a 403 means the request reached Anthropic (or a proxy in front of it) and was refused for this account, this credential or this model. It is not a usage limit. Anthropic’s API docs define 403 permission_error as “Your API key does not have permission to use the specified resource” (verified Nov 5, 2026). Usage limits come back as their own messages, which I’ll get to below.
The cruel part is the prefix. Claude Code says “Please run /login”, you run /login, and the same 403 comes back. The reporter in #99837 says it happened “repeatedtly even though im logged in. Tried logging out and logging back in and nothing.” It’s Dennis Nedry wagging his finger on the monitor in Jurassic Park: “Ah ah ah, you didn’t say the magic word.” Except you did say it. Several times.
Which 403 do you have?
Read the part after “403”. That’s where the cause is.
| Message | Likely cause | Fix |
|---|---|---|
| Request not allowed | Account, role or proxy | Check plan, role, proxy |
| Access grant | Model your account can’t use | Switch model |
| Permission denied | Credential refused | /status, then re-login |
| HTML “403 Forbidden” | Proxy or gateway | Check base URL setup |
| Missing scope (MCP) | Token lacks a scope | Re-auth the server |
Causes from the issues and docs listed under each section below, verified Nov 5, 2026.
“Request not allowed” after you log in
Anthropic documents this one by name. Its troubleshooting page has a section called “403 Forbidden after login” for API Error: 403 Request not allowed, and it lists three causes (verified Nov 5, 2026):
- Claude Pro, Max or Ultra users: your subscription may not be active. Check it at claude.ai/settings.
- Anthropic Console users: your account needs the “Claude Code” or “Developer” role. Admins assign it on the Console’s Members page.
- Behind a proxy: “corporate proxies can interfere with API requests.” The docs send you to the network configuration page.
The #50411 report was on v2.1.114 on macOS, marked as a regression, and closed the same day it was opened. There’s no maintainer explanation in the thread, so the docs above are the best official answer as of Nov 5, 2026.
“Access to this model requires an access grant”
This is #99837: opened Oct 6, 2026 on v2.1.290 (Linux), labeled area:auth, and still open with no maintainer reply as of Nov 5, 2026. Two other users confirmed it within the hour. One said: “I’m getting this error if I use Opus but not if I use Sonnet.”
So the message is about a model, not your login. Anthropic hasn’t published a doc entry for this exact string as of Nov 5, 2026, so I can’t tell you why a specific account lacked the grant. What the thread does show: logging out and back in didn’t fix it, and switching models worked for at least one person. Honestly, that’s maddening: a paying customer gets refused a model and the error says “log in again.” That deserves an official note. There isn’t one.
“Permission denied” (permission_error)
#51610 (Apr 21, 2026, v2.1.116, macOS) is the JSON permission_error version. The reporter had “already logged in” and “tried reinstalling Claude Code.” One commenter blamed the terminal app; the reporter then got it in a second terminal too. It was closed as inactive on May 27, 2026, with no fix. Anthropic’s API docs say to check “your organization’s access and workspace settings in the Claude Console” for this error type (verified Nov 5, 2026). That matters most if you’re on an API key.
HTML “403 Forbidden” through a proxy or gateway
#49885 (Apr 17, 2026, v2.1.112) used Claude Code with LiteLLM and Amazon Bedrock. Loading a skill returned an HTML page:
Please run /login · API Error: 403 <html>
<head><title>403 Forbidden</title></head>The reporter said it worked if they added /debug first, and suspected ANTHROPIC_BASE_URL wasn’t being passed through during skill execution. It was closed as stale, with no fix confirmed. If your 403 is an HTML page, a proxy or gateway sent it, not Anthropic’s JSON API.
Claude Code’s error reference also has an official gateway message, added in v2.1.273 (verified Nov 5, 2026):
Gateway refused the request · signing in again won't change this — check with your gateway administrator · API Error: 403 ...The docs say it plainly: “Signing in again doesn’t change a refusal.” Ask your gateway admin. Bedrock, Google’s Agent Platform and Microsoft Foundry have their own 403 entries in the same reference, mostly pointing at cloud IAM permissions and model access.
MCP “missing scope”
#94044 (Sep 13, 2026, Max account, Windows) got this when reconnecting the Claude Design MCP server:
Failed to reconnect to claude-design: api.anthropic.com rejected your claude.ai login (HTTP 403). Your token may be missing a scope this server needs — run /login and retry, or check that your account has access.It was closed as a duplicate of #92215, which was still open as of Nov 5, 2026. For MCP servers in general, the error reference says a server can refuse a tool call with HTTP 403 insufficient_scope, and the fix is to run /mcp, select the server and authenticate again (verified Nov 5, 2026).
How to fix Claude Code API Error 403, in order
Each step says where it comes from.
- Run
/statusfirst. Claude Code’s troubleshooting page says to “Run/statusinside Claude Code to confirm which authentication method is active” (verified Nov 5, 2026). You want to know whether you’re on your subscription login, an API key or a gateway before you change anything. - Check for an
ANTHROPIC_API_KEYyou forgot about. When that variable is set and approved, “Claude Code uses that key instead of your subscription’s OAuth credentials,” and in-pmode “the key is always used when present” (troubleshooting docs, verified Nov 5, 2026). Anthropic’s help center adds that this switches you to API usage charges (support.claude.com 11145838, verified Nov 1, 2026). Unset it, and remove it from your shell profile, if you meant to use your plan. - Do a clean re-login. The docs’ “Reset your login” steps: run
/logout, close Claude Code, startclaudeagain and sign in (verified Nov 5, 2026). It failed for some reporters, but it’s cheap and fixes real token problems. - Check your plan and role. Pro, Max and Ultra: confirm the subscription is active at claude.ai/settings. Console accounts: confirm the “Claude Code” or “Developer” role on the Members page (docs, verified Nov 5, 2026).
- On “access grant”, switch models with
/model. One #99837 commenter got it on Opus and not on Sonnet. Use a model your account can reach while the issue is open. - Behind a proxy, gateway or LiteLLM? Check that layer. Look at
ANTHROPIC_BASE_URLand the proxy’s own logs. A gateway refusal won’t clear by signing in again, per the docs. - Check status.claude.com. Several #99837 users hit the same error within an hour of each other. If many people report the same 403 at once, it’s worth checking for an incident.
- Still stuck? File it with
/feedbackand include the full error line and your version.
What not to do: don’t make a second account, don’t route through some “unlock” relay, and don’t share someone else’s key. A 403 is Anthropic saying no to this request, and Willy Wonka’s “You get nothing! You lose! Good day, sir!” is what you’ll get from those workarounds too, plus a terms-of-service problem.
403 vs 401 vs 429
| Code | Meaning | Read |
|---|---|---|
| 403 | Refused for this account | You’re here |
| 401 | Credential invalid | Invalid API key |
| 401 expired | Login expired | OAuth session expired |
| 400 | Request malformed | API Error 400 |
| Limit message | Usage cap hit | Usage limit reached |
Meanings from Anthropic API errors and the Claude Code error reference, verified Nov 5, 2026.
Short version: a 401 means Anthropic doesn’t accept who you are (Claude Code invalid API key, or Claude Code OAuth session expired if your saved login lapsed). A 403 means it knows who you are and still says no. A 400 is a broken request (Claude Code API Error 400), and a session or weekly cap is Claude Code usage limit reached.
Does a 403 use up my Claude usage?
Not published as of Nov 5, 2026, so I won’t guess. Plan names, if you’re reading older posts: Pro, Max ($100) and Ultra ($200, formerly Max 20x) (support.claude.com 17728952, verified Nov 1, 2026).
Here’s what I’d do
Run /status and read the line after “403”. “Request not allowed”: check your plan is active, kill any stray ANTHROPIC_API_KEY, do one clean /logout and login. “Access grant”: switch models and watch #99837. HTML page or “gateway refused”: that’s your proxy, so talk to whoever runs it. MCP “missing scope”: re-authenticate from /mcp.
If 403s keep eating your workday, it’s fair to have a backup ready. Our Claude Code alternatives list and AI coding tools compared page cover the options with dated prices.
Getting 401 instead of 403? That’s auth, not permission: Claude Code API Error 401.
A 429 is a rate limit, not a permission error: Claude Code API Error 429.
FAQ
What does Claude Code API Error: 403 Request not allowed mean? Anthropic refused the request for your account; its docs say check your subscription is active, your Console role, or a proxy in the way.
Does API Error 403 mean I hit my Claude usage limit? No, a 403 is a permission refusal, and usage limits show their own session or weekly limit messages.
Why does Claude Code say access to this model requires an access grant? Your account was refused for that model; in GitHub issue #99837 one user got it on Opus but not Sonnet, and the issue was open with no official fix as of Nov 5, 2026.
How do I fix API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}?
Run /status, remove any stray ANTHROPIC_API_KEY, do a clean /logout and login, and confirm your plan or Console role.
Will running /login fix a 403? Sometimes; it fixes token problems, but Anthropic’s docs say a gateway refusal won’t clear by signing in again.
Sources
- Claude Code GitHub issue #50411 (“Request not allowed” 403 after /login; closed): https://github.com/anthropics/claude-code/issues/50411 (verified 2026-11-04, re-checked 2026-11-05)
- Claude Code GitHub issue #99837 (“Access to this model requires an access grant”; open): https://github.com/anthropics/claude-code/issues/99837 (verified 2026-11-04, re-checked 2026-11-05)
- Claude Code GitHub issue #51610 (permission_error “Permission denied” on login; closed as inactive): https://github.com/anthropics/claude-code/issues/51610 (verified 2026-11-04, re-checked 2026-11-05)
- Claude Code GitHub issue #49885 (HTML 403 Forbidden on skill load via LiteLLM; closed as stale): https://github.com/anthropics/claude-code/issues/49885 (verified 2026-11-04, re-checked 2026-11-05)
- Claude Code GitHub issue #94044 (HTTP 403 missing scope for Claude Design MCP; duplicate of #92215): https://github.com/anthropics/claude-code/issues/94044 (verified 2026-11-04, re-checked 2026-11-05)
- Claude Code GitHub issue #92215 (Claude Design MCP 403s; open): https://github.com/anthropics/claude-code/issues/92215 (verified 2026-11-05)
- Claude Code troubleshooting, Login and authentication (403 Forbidden after login, Reset your login, ANTHROPIC_API_KEY override, /status): https://code.claude.com/docs/en/troubleshoot-install (verified 2026-11-05)
- Claude Code error reference (Gateway refused the request, MCP insufficient_scope, cloud provider 403s): https://code.claude.com/docs/en/errors (verified 2026-11-05)
- Anthropic API errors (403 permission_error): https://docs.claude.com/en/api/errors (verified 2026-11-05)
- Anthropic help, Use Claude Code with your Pro, Max or Ultra plan (ANTHROPIC_API_KEY means API charges): https://support.claude.com/en/articles/11145838-use-claude-code-with-your-pro-max-or-ultra-plan (verified 2026-11-01)
- Anthropic help, What is the Ultra plan (Max 20x renamed Ultra): https://support.claude.com/en/articles/17728952-what-is-the-ultra-plan (verified 2026-11-01)
- Claude status page: https://status.claude.com (reachable 2026-11-05)