---
title: "Revoke API key"
method: DELETE
path: "/api-keys/{id}"
---

# Revoke API key

`DELETE /api-keys/{id}`

## Request

- Base URL: `https://app.yoping.me/api/v1`
- URL: `https://app.yoping.me/api/v1/api-keys/{id}`
- Auth: API key in cookie `yp_session`

Revokes an API key. A missing or foreign key id returns 404.

## Path parameters

- `id` string, required

## Response `200`

Key revoked.

- object: Uniform success envelope: the payload is always under `data`.
  - `data` object, required
    - `revoked` boolean, required

## Other responses

- `401`: Not authenticated (code `unauthorized`): missing, invalid, or expired session; invalid login credentials; or a Bearer token, which this surface rejects.
- `403`: Forbidden. Code `forbidden` for a cross-origin (CSRF) request blocked by origin validation or for API-key management attempted without a browser session; `account_suspended` when a suspended account attempts a mutation; `account_deleted` when an account in its deletion grace window calls a non-exempt route.
- `404`: Not found (code `not_found`). A resource id belonging to another account is indistinguishable from a missing one.
- `429`: Too many requests (code `rate_limited`). A global per-IP budget of 300 requests/minute (burst 60) applies to every endpoint; login, signup, and test alerts have tighter dedicated limits.

---

[API](https://skmtc.dev/yoping/apis/yopingme-api.md) · [All operations](https://skmtc.dev/yoping/apis/yopingme-api/llms.txt) · [OpenAPI document](https://skmtc.dev/yoping/apis/yopingme-api/revisions/76d8deb40173?raw)