> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kash.bot/llms.txt
> Use this file to discover all available pages before exploring further.

# API_KEY_REVOKED

> HTTP 401 — API key revoked

**HTTP status:** 401 · **Title:** "API key revoked"

## When it fires

The key is well formed and recognised, but it has been revoked.

## Why it happens

* You or a teammate revoked it in the Kash web app (Settings → API Keys → Revoke).
* ZeroID revoked it, for example after a suspected leak.
* Automated security controls revoked it after anomalous activity.

## How to fix

* If the revocation was unexpected, contact ZeroID support. Every revocation is recorded with who, when and why.
* If you need to keep working, **issue a new key**. A revoked key cannot be reinstated; that is the security property.
* Update every place the old key was stored (environment variables, secret stores, CI configuration) when you roll out the new one.

## Related codes

* [`API_KEY_INVALID`](https://docs.kash.bot/developer-docs/api-errors/API_KEY_INVALID) — the key was deleted, not revoked
* [`API_KEY_EXPIRED`](https://docs.kash.bot/developer-docs/api-errors/API_KEY_EXPIRED) — the key reached its expiry date
* [`ORGANIZATION_INACTIVE`](https://docs.kash.bot/developer-docs/api-errors/ORGANIZATION_INACTIVE) — the key is fine but its account is suspended or cancelled


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.