Skip to content

Revoke API Key

Revoke a key. It stops working at once.

DELETE/api/v1/api-keys/{key_id}

Requires an API key with the admin scope.

N e Not available while acting as a client workspace. API keys are never created, listed or revoked over MCP. A key may revoke itself. The row is kept and the call writes an audit.api_key.revoked entry.

Path Parameters#

key_idstringpathrequired

The key identifier from List API Keys.

Response#

Returns { "data": { "id", "revoked": true } }.

Errors#

StatusDescription
401Missing, invalid, revoked or expired API key
403The key lacks the admin or write scope, or its creator lacks the required role
403Called while acting as a client workspace with X-Workspace-Id (acting_as_forbidden)
400Already revoked
404Key not found in this workspace

Rate Limit#

  • 120 requests per minute, shared by every write call in your workspace. Fixed 60-second window.
  • Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset (unix epoch seconds) and X-RateLimit-Bucket (write).
  • A 429 response includes a Retry-After header (seconds until the bucket resets).

For client-side patterns, see Rate Limiting.

Was this page helpful?
View as MarkdownLast updated November 4, 2026