---
title: "Schedule account deletion"
method: POST
path: "/account/delete"
---

# Schedule account deletion

`POST /account/delete`

## Request

- Base URL: `https://app.yoping.me/api/v1`
- URL: `https://app.yoping.me/api/v1/account/delete`
- Auth: API key in cookie `yp_session`

Verifies the caller's password and soft-deletes the account with a 7-day grace window during which /account/restore can undo it. An incorrect password returns 400.

## Request body

- AccountDeleteRequest
  - `password` string, required: The caller's current password, re-verified before deletion.

## Response `200`

Deletion scheduled.

- object: Uniform success envelope: the payload is always under `data`.
  - `data` object, required
    - `deleted_at` string, date-time, required
    - `purge_after` string, date-time, required
    - `message` string, required

## Other responses

- `400`: Invalid input (code `validation_failed`): malformed JSON, a missing or out-of-range field, bad pagination parameters, or a rejected token.
- `401`: Not authenticated (code `unauthorized`): missing, invalid, or expired session; invalid login credentials; or a Bearer token, which this surface rejects.
- `403`: Forbidden. Code `forbidden` for a cross-origin (CSRF) request blocked by origin validation or for API-key management attempted without a browser session; `account_suspended` when a suspended account attempts a mutation; `account_deleted` when an account in its deletion grace window calls a non-exempt route.
- `429`: Too many requests (code `rate_limited`). A global per-IP budget of 300 requests/minute (burst 60) applies to every endpoint; login, signup, and test alerts have tighter dedicated limits.

---

[API](https://skmtc.dev/yoping/apis/yopingme-api.md) · [All operations](https://skmtc.dev/yoping/apis/yopingme-api/llms.txt) · [OpenAPI document](https://skmtc.dev/yoping/apis/yopingme-api/revisions/76d8deb40173?raw)