---
title: "Revoke Key"
method: DELETE
path: "/v1/auth/keys/{key_id}"
tags: ["Authentication & API Keys"]
---

# Revoke Key

`DELETE /v1/auth/keys/{key_id}`

## Request

- Base URL: `https://api.vectelos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.vectelos.com/v1/auth/keys/{key_id}`
- Auth: none declared

Revoke one API key. It stops authenticating immediately.

Until this existed there was no way to kill a leaked key short of editing
Firestore by hand -- and a `vt_live_` key pasted into a customer's CI log is
the ordinary way that happens, not an exotic one.

## Path parameters

- `key_id` string, required

## Headers

- `authorization` string, nullable: Bearer <JWT session token>

## Cookies

- `vx_session` string, nullable

## Response `204`

Successful Response

## Other responses

- `422`: Validation Error

---

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