✓ Fact-checked June 24, 2026
Sources: Anthropic Acceptable Use Policy · Anthropic Support Docs · Anthropic API Reference
Why Does Claude Say "This Organization Has Been Disabled"?
You open Claude Console, make an API call, or log into Claude for Work — and hit this error. Access stops immediately across every key in your org. Here is exactly what it means, the five causes ranked by how often each occurs, the fastest path to diagnosis, and a support contact template that minimises back-and-forth.
Error: This organization has been disabled
Direct Answer
Anthropic has suspended your API organization account. All API keys under the org stop working simultaneously. This appears in Console, in API calls (HTTP 403 with error_code "organization_disabled"), and on claude.ai for Work. Your data is not deleted. The five causes, most-to-least likely: (1) failed billing invoice; (2) automated safety or abuse flag from high-volume or unusual usage; (3) leaked API key used by someone else in violation of the ToS; (4) Acceptable Use Policy violation; (5) terms update requiring re-acceptance. Check billing first — it resolves in hours if that is the cause. Everything else requires contacting support.
Claude Limits — Complete Guide Series
What This Error Actually Means — and What It Does Not
Claude's API is structured around "organizations" — the legal and billing entity that owns API keys, usage data, and team seats. When Anthropic disables an organization, it immediately invalidates all API keys associated with that org. Every system, every key, every integration stops working at once.
This is distinct from:
- A single API key being revoked — other keys in the org would still work. If you see organization_disabled, all keys are affected.
- A rate limit error (429) — rate limits reset in seconds to minutes. An org disable requires support resolution.
- A personal claude.ai account suspension — your personal account (if separate from the org) is unaffected. Only API access and claude.ai for Work tied to that org are suspended.
- Data deletion — suspension freezes access. All your data (conversations, Projects, files, usage logs) remains intact and is fully restored when re-enabled.
The API Error Response (For Developers)
If your code is calling the Anthropic API, a disabled org produces this response:
HTTP/1.1 403 Forbidden
Content-Type: application/json
{
"type": "error",
"error": {
"type": "permission_error",
"message": "This organization has been disabled."
}
}
The HTTP 403 distinguishes this from:
| HTTP Status | Error Type | Cause | Fix |
|---|
| 401 Unauthorized | authentication_error | Invalid or expired API key | Generate a new key or verify key string |
| 403 Forbidden | permission_error (org disabled) | Organization suspended | Check billing / contact support |
| 429 Too Many Requests | rate_limit_error | Exceeded token or request rate limit | Wait and retry with exponential backoff |
| 529 Overloaded | overloaded_error | Server under high load | Retry after a short delay |
If your monitoring system treats 403 as "invalid key" and rotates keys automatically: Creating new keys will not fix organization_disabled errors. The 403 is at the org level, not the key level. Your key rotation logic needs to detect this specific error type and alert humans rather than auto-rotating.
The 5 Causes — Ranked by Likelihood
A credit card charge failed — expired card, over-limit card, bank blocking a foreign charge — and after one or more retry attempts, Anthropic suspended the org. This is the fastest to fix: pay the overdue invoice at platform.anthropic.com → Billing → Invoices, update the payment method if needed, and most accounts auto-re-enable within 1–2 hours without needing to contact support.
How to check: Go to platform.anthropic.com → Billing. If you see an invoice marked "Failed," "Overdue," or a yellow/red billing banner, this is the cause. The invoice will show the amount due and the card that failed.
Common scenario: A card expired last month, Anthropic retried 3 times, sent email to the billing address (which may have gone to spam), then suspended after no payment. The account was working fine until the grace period ended.
Anthropic's automated systems monitor API usage patterns. Certain patterns statistically correlate with abuse and trigger automatic suspension before a human reviews the account. Common triggers:
• Rapid request volume that exceeds what a human could generate manually
• Usage from multiple geographic IP addresses simultaneously (suggests shared or leaked key)
• Prompts containing specific keywords across many requests in short succession
• Request patterns that look like automated scraping, bulk content generation, or safety probing
• Sudden large spike vs. normal baseline (product launch, batch job) with no prior communication
This type of suspension frequently catches legitimate users. A batch processing job, a load test before launch, or a new customer-facing product that suddenly drives real traffic can all trigger the same signals as actual abuse. The fix: contact support with a clear explanation of your use case and what you were doing when the suspension happened.
Your API key was exposed somewhere — a public GitHub repository, client-side JavaScript, a committed .env file, a screenshot, a Slack message, a paste bin — and someone else found and used it. They may have used your key for abusive purposes (bulk generation, safety circumvention, large-scale API abuse) that triggered Anthropic's monitoring.
Under the Anthropic Terms of Service, you are responsible for all usage under your API keys, regardless of whether you were the one who made the calls.
Immediate action if you suspect this: Rotate all API keys immediately at platform.anthropic.com → API Keys → Revoke each key. Do this before contacting support — having already rotated your keys demonstrates you took responsible action and speeds up re-enablement.
How to find a leaked key: Search GitHub (github.com/search) for your key prefix (the first 20 characters, typically "sk-ant-api03-..."). Check your git history: git log -p | grep "sk-ant". Check any .env files that may have been committed to version control.
A human review at Anthropic found that usage in your org violated the Acceptable Use Policy. Anthropic's AUP specifically prohibits: generating content that sexually exploits minors, creating weapons capable of mass casualties, building deceptive systems that impersonate humans without disclosure, generating content for large-scale disinformation, and circumventing safety systems.
Violations can come from: your own usage, a team member's usage, or (in the leaked key scenario) someone who used your key. The key distinction from cause 2 is that cause 2 is automated and presumptive — support can typically reverse it quickly once you explain your legitimate use. Cause 4 involves a human determination that a specific policy was violated — the resolution timeline is longer and the outcome is not guaranteed.
If you believe your org was flagged for AUP violation in error, the appeal process requires explaining the specific nature of the usage that triggered the flag and demonstrating it does not fall under the prohibited categories.
Anthropic occasionally updates their Terms of Service and requires org admins to actively re-accept. In some cases, if the admin does not acknowledge new terms within a deadline, the org may be suspended until terms are accepted. This is uncommon and typically preceded by email notifications to the billing address.
Fix: Log into platform.anthropic.com and check for any terms update banners or prompts. If a terms re-acceptance is required, accepting it typically re-enables access immediately.
Step-by-Step Diagnosis — In This Order
1
Check billing at platform.anthropic.com → Billing
This takes 30 seconds and resolves 50%+ of org suspensions. Look for: a red or yellow billing banner, any invoice with status "Failed," "Overdue," or "Unpaid." If found: update the payment method if the card has changed, then pay the overdue invoice. Account typically auto-re-enables within 1–2 hours once payment clears. No support contact needed.
2
Check the billing email inbox
Anthropic sends email to the billing address on the org account when taking suspension action. Check that inbox and its spam/junk folders for emails from any @anthropic.com address. The email will state the reason for suspension, which tells you which cause you are dealing with and what action to take. If you find it, do not reply to that email — use the support form instead (replies to automated emails often go unread).
3
Check API key security
Search GitHub and any public code repositories for your API key prefix. Review your own git history for accidentally committed .env files or credentials. Check if any team member recently shared a key in Slack, Notion, or a paste service. If you find a leaked key, rotate all keys immediately at platform.anthropic.com → API Keys → select each → Revoke — then note the date for your support request.
4
Review usage logs for anomalies
In Console → Usage, review the last 7–14 days. Look for: unusual spikes in request volume, requests from unfamiliar time zones or IP ranges, unusually high token counts per request, or patterns that differ from your normal usage. Understanding what happened in the days before the suspension helps you explain your situation to support and identify whether this was a legitimate usage spike or a key compromise.
5
Check for terms update prompts
Log into platform.anthropic.com with the org admin account. If there is a terms update requiring action, you will see a banner or modal requiring acceptance. Accepting immediately re-enables access if this was the cause.
6
File a support request with complete information
If billing is current, keys are secured, and there is no terms prompt: go to support.anthropic.com and file a support request. Use the template below. The most important thing: provide everything upfront. Support agents must look up your account before they can act — giving them your org ID, billing email, timeline, and use case description in the first message eliminates the round-trip delay of waiting for them to ask for this information.
The Support Request Template That Gets the Fastest Response
Subject: Organization Disabled — [ORG NAME / ORG ID] — Request Re-enable
Organization ID: org-xxxxxxxxxxxxxxxx
(Find this: platform.anthropic.com → Settings → Organization → Organization ID)
Billing email on account: your@company.com
Error started: [Date and approximate UTC time — e.g., "June 24, 2026, around 14:30 UTC"]
Error message:
"This organization has been disabled"
(Also appearing as HTTP 403 with error_code: permission_error on API calls)
Steps I have already taken:
1. Billing check: [Current / Paid overdue invoice on [date] / No invoice issues found]
2. API key security: [No leaked keys found / Rotated all keys on [date] / Still investigating]
3. Usage review: [Normal / Batch job ran [date] / Usage spike on [date] / Unfamiliar activity]
4. Billing email: [Received email re: [reason] / Nothing found in inbox or spam]
Our use case (be specific):
[Example: "We run a B2B SaaS product that uses Claude Sonnet 4.6 to
generate first-draft content for e-commerce product listings.
Typical volume: ~2,000 API calls/day, 500-1,000 tokens each.
We ran a batch job on June 23 processing ~50,000 product descriptions
as a migration task — this was the highest-volume day we have had."]
Business impact:
[Example: "Our product is down for 200 paying customers. Every hour
of suspension costs approximately $X in customer churn risk."]
What I need:
Re-enable the organization account and clarification on what triggered
the suspension so we can prevent recurrence.
Thank you.
File at support.anthropic.com, not by email: Support form requests are routed to the right team, create a trackable ticket, and get faster responses than emailing addresses directly. If you have a Team or Enterprise plan, you may have access to a dedicated Slack channel or account manager — use those for the fastest resolution. For enterprise accounts, also try emailing support@anthropic.com directly as a backup.
Expected Re-Enable Timelines by Cause
| Cause | Re-enable Time | What You Need to Do | Is Human Review Required? |
|---|
| Failed invoice — paid immediately | 1–2 hours (often automatic) | Pay overdue invoice; update payment method if expired | No |
| Automated safety flag (legitimate use) | 24–48 business hours | Support request with org ID and use case explanation | Yes |
| Leaked key / third-party misuse | 24–72 hours | Rotate all keys + support request with timeline and explanation | Yes |
| Terms update | Immediate (after acceptance) | Accept updated terms in Console | No |
| AUP violation (first offense) | 3–7 business days | Support request, formal review, may require commitments about future use | Yes — formal review |
| AUP violation (repeat / severe) | Permanent | Formal appeal only — outcome not guaranteed | Yes — legal/trust team |
If You Are an Employee — Not the Org Admin
The org suspension is on the company's Anthropic account. If you are an employee who uses Claude for Work or whose company's product uses the API, you cannot resolve this yourself unless you are a Console admin with billing access.
The path when you are not the admin:
- Identify who in your company manages the Anthropic Console account. Usually: the engineering lead, platform engineer, or CFO/finance (whoever set up billing).
- Share this page with them — the diagnostic steps and support template are what they need.
- Give them the timestamp when you first saw the error — this helps them correlate with usage logs and billing events.
- Your personal claude.ai account, if separate from the company org, is unaffected. You can continue using your personal account for personal tasks while the company account is being resolved.
If your entire engineering team is blocked: The fastest path is whoever has billing admin access to platform.anthropic.com — that person can check the invoice status and pay immediately if billing is the cause, potentially restoring access within hours. Do not wait for support if billing is the cause.
Prevention: How to Avoid This Happening Again
Use separate API keys per project
Never use one shared API key across your entire stack. Create a dedicated key for each project, service, or integration at platform.anthropic.com → API Keys → Create Key. Name each key clearly (e.g., "production-content-generator-v2", "staging-test-suite"). If one key is compromised or one project triggers a flag, only that key needs rotation — not your entire infrastructure. Your other services keep running.
Set a hard monthly spend limit
In Console → Billing → Spend Limits, set a hard cap on monthly API spend. This prevents a bug, an infinite loop, or a leaked key from generating thousands of dollars of charges that lead to a billing suspension or an unexpectedly large failed payment. The cap halts API calls when the limit is reached (your integration gets 529 errors) rather than accruing charges you cannot pay.
Enable billing alerts at 50% and 80% of budget
Console → Billing → Usage Alerts. Setting email alerts before you hit your limit gives you time to investigate unexpected spikes, update your payment method if it is about to expire, and avoid the scenario where you discover a problem after the account is already suspended. Most billing suspensions happen because the account holder never saw the failed payment email.
Notify Anthropic of planned usage spikes
If you are planning a batch job, a load test, a product launch, or any event that will drive dramatically more traffic than your normal baseline, email support@anthropic.com in advance with a brief note: "We are running a batch migration on [date], expecting approximately 10× our normal daily volume. Wanted to notify you proactively." This communication creates a record that explains the spike and prevents automated systems from flagging it as abuse.
Rotate API keys quarterly
Generating new API keys quarterly and revoking old ones limits the blast radius of any key compromise. A key that was accidentally exposed 6 months ago but has since been rotated cannot be used against your org today. Set a calendar reminder to rotate keys on a schedule.
Never commit API keys to version control
Use environment variables for all API keys. Add .env to your .gitignore. Use secret management services (AWS Secrets Manager, HashiCorp Vault, Doppler) for production credentials. Run GitHub secret scanning to catch any accidentally committed keys. These are the most common vectors for key leaks that lead to org suspensions.
Frequently Asked Questions
What does "this organization has been disabled" mean on Claude? +
Anthropic has suspended your API organization account. All API keys in the org are immediately invalidated. The error appears in Claude Console, via HTTP 403 in API calls (error_code: permission_error, "This organization has been disabled"), and on claude.ai for Work. Your data is not deleted. The five causes ranked by likelihood: unpaid invoice, automated safety flag, leaked API key misused by others, AUP violation, or terms update requiring re-acceptance.
How do I get my Claude organization re-enabled? +
Check billing first at platform.anthropic.com. If an invoice is overdue, pay it — the account often auto-re-enables within 1–2 hours. If billing is current, check the billing email inbox for a message from Anthropic explaining the suspension. Then file a support request at support.anthropic.com with your organization ID, billing email, when the error started, a summary of recent activity, and your use case description. Include everything in the first message to avoid round trips.
Does this error delete my data? +
No. Org suspension freezes API access and Console login but does not delete data. All conversation history, Projects, uploaded files, custom prompts, and API logs remain intact. When re-enabled, everything is accessible exactly as you left it. Only permanent account closure — for serious repeat AUP violations — triggers Anthropic's data deletion process under their retention policy.
What HTTP status code does the API return for a disabled org? +
HTTP 403 Forbidden with a JSON body containing "type": "permission_error" and message "This organization has been disabled." This is distinct from 401 (invalid key), 429 (rate limit), and 529 (server overload). Creating new API keys will not fix a 403 with organization_disabled — the suspension is at the org level and must be resolved via billing or support.
Can the org be disabled by mistake? +
Yes, frequently for legitimate high-volume users. Anthropic's automated systems flag patterns that statistically correlate with abuse — batch jobs, product launches, load tests, or API keys accessed from multiple IPs can all trigger automatic suspensions. Explaining your use case to support typically resolves automated flags within 24–48 hours. This is the second most common cause of org suspensions after billing failures.
How long until the org is re-enabled? +
Depends on the cause. Billing failure after payment: 1–2 hours, often automatic. Automated safety flag (legitimate use): 24–48 business hours. Leaked API key: 24–72 hours after rotation and support explanation. Terms update: immediate after accepting. AUP violation (first offense): 3–7 business days with human review. Serious/repeat AUP violation: permanent suspension, formal appeal only.
More in This Series