---
title: "Delete your account"
method: POST
path: "/management-console/account/delete"
tags: ["Your account"]
---

# Delete your account

`POST /management-console/account/delete`

## Request

- Base URL: `https://verifiedhandles.org`
- URL: `https://verifiedhandles.org/management-console/account/delete`
- Auth: HTTP bearer

Deletes the account at once and for good: every session and API key (this one too), the profile, preferences and unpublished submissions and unsaved drafts. What it added to entries stays on the record under an anonymous deleted account. A blocked account may delete itself. There is no undo and no dry run.

## Other responses

- `302`: No key was sent: the console sends a browser to sign in. A script should send its key.
- `303`: Deleted: on to the page that confirms it. `?err=blocked_no_key` on the account page instead when a blocked account’s block could not be kept, and nothing was deleted.
- `400`: The request sent a key and a session cookie together (`bearer_with_cookie`): send one.
- `401`: The key was refused: unknown, revoked or expired, its holder may no longer use keys, or this instance takes none. Carries `WWW-Authenticate: Bearer`.
- `403`: The key’s account lacks the capability, or is blocked: the body is the word `Forbidden`. A read-only key that tries to change something is refused first, as JSON: `{"error":"read_only_key"}`.
- `429`: Too many changes in the last minute: counted per IP address, per account and per key (an admin key’s per key alone, at the limit set on Console → Rate limits). Wait the number of seconds `Retry-After` gives.
- `503`: The site is down for maintenance. The body is the maintenance page, as HTML. Try again later: `Retry-After` gives the seconds.

---

[API](https://skmtc.dev/verifiedhandles/apis/verified-handles-api.md) · [All operations](https://skmtc.dev/verifiedhandles/apis/verified-handles-api/llms.txt) · [OpenAPI document](https://skmtc.dev/verifiedhandles/apis/verified-handles-api/revisions/40720de2e0ec?raw)