- Revoke stops the key at once and moves it to Revoked Keys, where it stays as a record of what had access. The confirmation is “API key revoked”.
- Delete stops the key at once, if it’s still live, and removes it for good. Revoked keys can be deleted too. The confirmation is “API key deleted”.
What happens
The key stops authenticating at once. Anything using it — a script, a CI job, a scheduled integration — starts failing on its next request. There’s no grace period and no way to un-revoke; recovering means creating a new key and updating every consumer.Revoke or delete?
Revoke when you want the history: the key’s name, access, and last-used date stay on the page, so later you can still see what had access and when it was last used. Delete when the record isn’t worth keeping — a key made by mistake, or one revoked long ago.Revoke when
- The key leaked. Committed to a repository, pasted into a chat, included in a screenshot. Revoke first and investigate afterwards — the cost of a false alarm is far lower than the cost of waiting.
- Someone with access left. Keys aren’t tied to a person and keep working after a member is removed from the organization. Removing someone from Users does not revoke keys they created or held.
- The integration is retired. Decommissioned service, cancelled project, abandoned experiment.
- It’s never been used. A key with no last-used date is a live credential doing nothing.
Rotating a key
There’s no rotate action, so do it in this order to avoid downtime:- Create a new key with a name marking it as the replacement.
- Update every consumer to the new key.
- Confirm the new key is working — check its Last used on the key list.
- Revoke the old key.
From the API
Both need an admin or owner, signed in — an API key can’t revoke or delete keys.GET /v1/organizations/{orgId}/api-keys lists them all; is_active is false for a revoked key.