---
title: "Revoke organization API key"
method: DELETE
path: "/orgs/{org_id}/api-keys/{key_id}"
tags: ["Organizations"]
---

# Revoke organization API key

`DELETE /orgs/{org_id}/api-keys/{key_id}`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/orgs/{org_id}/api-keys/{key_id}`
- Auth: HTTP bearer

Authorization: the caller must be a member of `org_id` (owner/admin, or the member who created the key), and `key_id` is matched together with `org_id`, so a key owned by another org returns 404 and no other tenant's key can be revoked.

## Path parameters

- `org_id` string, required
- `key_id` string, required

## Response `200`

Key revoked

- object
  - `revoked` boolean
  - `key_id` string

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)