---
title: "Schedule this account for deletion"
method: POST
path: "/v1/account/delete"
tags: ["account"]
---

# Schedule this account for deletion

`POST /v1/account/delete`

## Request

- Base URL: `https://api.hyperresearch.ai`
- URL: `https://api.hyperresearch.ai/v1/account/delete`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `hr_session`

Owner only, and `confirm_email` must be the account email typed exactly. Nothing is destroyed yet: the account keeps working for 14 days and the console shows a banner with a button to cancel. After that a job revokes every key and session, stops and refunds anything still running, deletes every workspace and its vault, removes the Stripe customer and the Clerk user, and anonymises what is left. An account with other people on it is refused until they are removed or ownership is transferred.

## Request body

- AccountDeleteRequest
  - `confirm_email` string, required: The account email address, typed exactly.

## Response `202`

Scheduled

- AccountDeletion
  - `status` 'scheduled' | 'purging' | 'purged' | 'null', nullable, required
  - `requested_at` string, nullable, required
  - `scheduled_for` string, nullable, required
  - `source` 'self_serve' | 'clerk_user_deleted' | 'null', nullable, required
  - `cancellable` boolean, required
  - `confirm_with` string, required
  - `other_members` integer, required

## Other responses

- `400`: Invalid request
- `401`: Authentication failed
- `403`: Insufficient scope or plan
- `404`: Not found
- `409`: Already being deleted, or ownership must be transferred first
- `429`: Rate limited or over quota
- `500`: Internal error

---

[API](https://skmtc.dev/hyperresearch/apis/hyperresearch-cloud-api.md) · [All operations](https://skmtc.dev/hyperresearch/apis/hyperresearch-cloud-api/llms.txt) · [OpenAPI document](https://skmtc.dev/hyperresearch/apis/hyperresearch-cloud-api/revisions/726ef831ebf4?raw)