Revoke a leaked or unused API key now
Stop a key authenticating, immediately and permanently, and read back when it happened. Takes a console session, so a key cannot revoke a key. Repeats are safe.
DELETE
This endpoint takes a signed-in console session, not an API key. Send the session cookies your browser received when you signed in, plus the
X-CSRF-Token header set to the value of the csrf_token cookie. A request authenticated with an arukz_sk_ key is refused with 403. See Managing API keys.
Revocation is:
- Immediate. The key fails authentication on the very next request. There is no cache to wait out.
- Terminal. A revoked key cannot be reactivated. To restore access, create a new key.
- Idempotent. Revoking a key that is already revoked succeeds and returns it unchanged, with its original
revoked_at.
200 with the revoked key rather than 204, so you can read revoked_at without a second request. The key stays in List API keys with status set to revoked.
A key that does not exist, a key in another organization and a malformed ID all return the same 404. You need the owner or admin role.
string
required
The key’s ID (UUID), as returned in
id.string
required
The value of your session’s
csrf_token cookie (named __Host-csrf_token when the console is
served over HTTPS without a shared cookie domain). Required on this request because it changes
state; a missing or mismatched token returns 401.Response
string
required
The key’s ID (UUID).
string
required
The key’s label.
string
required
arukz_sk_ followed by the first 8 characters of the ID. Not a secret.string
required
owner, admin, editor, normal or dataset_operator.string
required
Always
revoked.string
required
When the key was created, ISO 8601 in UTC.
string | null
required
ID of the user who created the key.
string | null
required
When the key would have expired, or
null.string
required
When the key was revoked, ISO 8601 in UTC.
string | null
required
When the key last authenticated a request, or
null if never.Last modified on September 26, 2026