---
title: "Confirm Key Reset Execute"
method: POST
path: "/api/keys/reset-confirm"
tags: ["API Keys"]
---

# Confirm Key Reset Execute

`POST /api/keys/reset-confirm`

## Request

- Base URL: `https://warnfirehose.com` (the document declares no server; this is the origin it was published from)
- URL: `https://warnfirehose.com/api/keys/reset-confirm`
- Auth: none declared

Execute the API key reset. Called by the form on the GET page.

Consumes the token, generates a new key, emails it, and shows it on
the response page. This is the mutating side of the double-confirm
pattern — the GET handler only renders the form so corporate email
scanners can't burn the token by pre-fetching the link.

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/warnfirehose/apis/laborcurrent-api.md) · [All operations](https://skmtc.dev/warnfirehose/apis/laborcurrent-api/llms.txt) · [OpenAPI document](https://skmtc.dev/warnfirehose/apis/laborcurrent-api/revisions/0040897972b8?raw)