> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blobhub.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Delete API Key

Revoke and delete a specific API key.

## **DELETE** `/api-keys/:id`

### Path Parameters

| Parameter | Type   | Required | Description                   |
| :-------- | :----- | :------- | :---------------------------- |
| `id`      | string | Yes      | The unique ID of the API key. |

### Response

Returns `{"status": "success"}` — no body beyond the status.

### Errors

| Status | Error       | Cause                                                                       |
| :----- | :---------- | :-------------------------------------------------------------------------- |
| 403    | `forbidden` | Missing `admin` access to the key's target, or no human behind the request. |

Revoking is a human act, the same as minting: a [service account](/general/service-accounts)'s own key gets
`403` for every key it tries to delete, including its own, whatever role it carries. A leaked key therefore
cannot revoke the key you would use to shut it down. Use an
[acting token](/rest-api/auth/impersonate) when automation genuinely has to revoke on a human's behalf.

### Example

<CodeGroup>
  ```bash Request theme={null}
  curl -X DELETE https://api.blobhub.io/v1/api-keys/key_001 \
    -H "X-API-Key: $ORG_API_KEY"
  ```

  ```json Response theme={null}
  {
    "status": "success"
  }
  ```
</CodeGroup>