# SEC_API_LEAK: Possible API key disclosure

- Module: SEC. Security, API keys, root grants, spam screening
- Severity: Critical
- Impact: Customers. End customers are affected (e.g. a missing e-mail, payment or order).
- Retry: Not retryable. Retrying will not help until the cause is fixed.
- Reference: https://docs.bizkithub.com/en/system-codes/SEC_API_LEAK

## What happened

A pattern consistent with a public API key being shared outside trusted channels was observed. Rotate the key and review recent usage.

## Likely causes

- Your organisation's API key was used to access a customer identity that belongs to a different organisation.
- The key was likely shared or exposed outside your trusted systems.

## How to resolve

1. Issue a new API key in the organisation settings and update all integrations.
2. Delete or deactivate the exposed key.
3. Review where the key is stored (public repositories, client-side code, shared configs).
4. Check the affected contact listed in the log entry and inform them if required by GDPR.

## Related codes

- SEC_API_NEW: New API key issued
- SEC_API_DEL: API key deleted
- SEC_API_RATE: API key rate limit exceeded
- SEC_ROOT_GRANTED: Root permission granted
- SEC_API_DEACT: API key deactivated
- SEC_API_EXP: API key expiration extended
