Developers & API
Governance

The controls that keep programmatic access safe.

Organization-level policy over every key: require an expiry, forbid never-expiring keys, require a service account for production, restrict by IP — and switch the whole API off in one place. Every request is logged and rate-limited.

Organization policy governs every key from one place: require an expiry, forbid never-expiring keys, require a service account for production traffic, and restrict by IP — or flip the whole API off instantly, so even a valid, unexpired key stops working. Every request is written to an audit log and subject to per-key rate limits, so programmatic access stays observable and bounded rather than a blind spot.

  • API policy — required expiry, no never-expiring keys, service-account-for-prod, IP allowlists.
  • Kill switch — disable the API org-wide instantly, even for valid keys.
  • Audited & rate-limited — every API request logged, per-key limits enforced.
api policy · acme
API enabledON
Expiration required on new keysON
Never-expiring keys allowedOFF
Service account required for productionON
IP restrictions allowedON