Create Erasure Request
Create a pending erasure request and issue a one-time token.
Returns 201 with the new request's state. The confirm_token field in the response is populated for password-auth users and null for OAuth users (Issue #469): OAuth users receive the token via email instead, keeping the raw secret out of the response surface.
Other status codes: - 403: user is the protected initial admin - 409: an active erasure request already exists for this user (ERASURE-006), or the user owns a workspace with a running paid subscription (BILLING-005, Issue #1940) - 503: OAuth user but the confirmation email failed to dispatch (mapped from EmailDispatchError); the pending row is rolled back so the user can retry once the email backend recovers.
The receipt notification (separate from the OAuth confirmation email) is dispatched post-commit and is fire-and-forget — it tells the user the request was received and is meant to be obvious to the human even if they don't click any confirm link.
Request
- Base URL: https://memory.kagura-ai.com (the document declares no server; this is the origin it was published from)
- URL: https://memory.kagura-ai.com/api/v1/me/account/erasure-request
- Auth: none declared
Headers
Response
Successful Response
Changes
No recorded changes to this operation across all 2 revisions of this API.