Revoke organization API key

DELETE /organizations/{org_id}/api_keys/{key_id}

Revokes the specified organization API key. An API key that is no longer needed can be revoked. This action cannot be reversed. API keys can also be managed in the Neon Console. See Manage API keys.

Markdown for AI context

curl "https://console.neon.tech/api/v2/organizations/$ORG_ID/api_keys/$KEY_ID" \
  -X DELETE \
  -H "Authorization: Bearer $NEON_API_KEY"

Every field below is optional. An empty body works too.

Also available in

neon api-keys revoke <id>

Organization

org_id

string

The Neon organization ID

Key ID

key_id

integer

The API key ID

200

Revoked the specified organization API key

"id": (integer),reqint64

"name": (string),req

"created_at": (string),reqdate-time

"created_by": (string),requuid

"last_used_from_addr": (string),req

"revoked": (boolean),req

"project_id": (string),

"last_used_at": (string),date-time

default

General error

This endpoint can return the standard Neon API error response.

Response fields

• message Required. Human-readable error message.
• code Required. Machine-readable error code.
• request_id Optional. Request identifier for debugging. You can provide one with the X-Request-ID header.

Retry guidance

If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.

Idempotent methods (GET, HEAD, OPTIONS) are generally safe to retry after a network error or timeout. Non-idempotent methods (POST, PATCH, DELETE, PUT) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.

Responses with 423 Locked or 503 Service Unavailable are safe to retry. 423 Locked means the resource is temporarily locked, usually because another operation is in progress.