Skip to main content
HTTP status: 409 · Title: “Active key limit reached”

​
When it fires

You tried to issue a new API key while your account already holds the maximum of 5 active (non-revoked) keys. The limit is per user, across all environments, and is enforced when a key is issued from the Kash web app (Settings → API Keys). It is not returned by the /v1/* endpoints themselves.

​
Why it happens

  • A genuine ceiling. Most integrations need two or three keys (one per environment, perhaps one for CI). The cap stops key pooling, which would otherwise let one account multiply its per-user rate limit.
  • A script that issues a fresh key on every run instead of reusing one.

​
How to fix

  • Revoke a key you no longer use (Settings → API Keys → Revoke), then issue the new one.
  • Reuse keys where it makes sense: one kash_live_… key for production code and one kash_test_… key for everything else.
  • If your integration genuinely needs more active keys, contact ZeroID support.
  • API_KEY_REVOKED — what you get if you keep using a key after revoking it