---
title: "Abandon Reauthorize"
method: DELETE
path: "/v1/accounts/{account_id}/reauthorize"
tags: ["accounts"]
---

# Abandon Reauthorize

`DELETE /v1/accounts/{account_id}/reauthorize`

## Request

- Base URL: `https://api.usekeel.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.usekeel.io/v1/accounts/{account_id}/reauthorize`
- Auth: none declared

Explicitly abandon a staged re-authorization session (spec 00b §2.5).

Retires ONLY the staged pending key and clears ``meta.pending_reauth``;
the live authorization — status, signer, expiry, execution path — is
untouched, exactly as if the reauth had never been started. Idempotent:
with no staged session this is a no-op 204, so duplicate abandon calls
converge.

The "only the pending key" guard is real, not assumed: the staged key's
state is read from the signing service first. A staged key that already
ACTIVATED (a partially-completed reauth whose venue-side swap succeeded)
is refused with 409 — abandoning at that point would retire the signer
the venue now recognizes; the recovery is to finish the swap by
re-running authorization.

## Path parameters

- `account_id` string, required

## Headers

- `Authorization` string, nullable
- `X-Org-Id` string, nullable

## Response `204`

Successful Response

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/usekeel/apis/keel-api.md) · [All operations](https://skmtc.dev/usekeel/apis/keel-api/llms.txt) · [OpenAPI document](https://skmtc.dev/usekeel/apis/keel-api/revisions/3191ca10b0ab?raw)