Named API keys you can rotate without downtime
Hold several API keys at once, name each one, see when it was last used, and revoke it on its own. Keys are now stored hashed and shown only once.
An account used to have exactly one API key, so replacing it broke every integration until the new value was deployed. There was also no way to keep separate keys for staging and production.
Keys now live under Settings, API & Webhooks, and you can have as many as you need. Rotating is a sequence with no gap in it: create a new key, deploy it, watch the old key’s last-used time stop moving, then revoke it.
Keys are stored as a one-way hash, so the full key is shown once, when it is created, and never again by anyone, us included. Your existing key carried over as "Default", and nothing about your integration had to change.