---
title: "Get Active Erasure Request"
method: GET
path: "/api/v1/me/account/erasure-request"
tags: ["account-erasure"]
---

# Get Active Erasure Request

`GET /api/v1/me/account/erasure-request`

## 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

Return the user's active erasure request, or null if none.

"Active" = pending OR cooling_off OR in_progress. Terminal states
(complete / failed / cancelled) are not surfaced here — that's an
admin-side audit concern, not user-facing UX.

## Headers

- `authorization` string, nullable

## Response `200`

Successful Response

- ErasureRequestStateResponse: Read-only view of an erasure request's lifecycle state.
  - `request_id` unknown, required
  - `status` unknown, required
  - `is_self_service` unknown, required
  - `requested_at` unknown, required
  - `confirmed_at` unknown
  - `scheduled_for` unknown
  - `started_at` unknown
  - `completed_at` unknown
  - `cancelled_at` unknown
  - `failure_reason` unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/kagura-ai/apis/kagura-memory-cloud.md) · [All operations](https://skmtc.dev/kagura-ai/apis/kagura-memory-cloud/llms.txt) · [OpenAPI document](https://skmtc.dev/kagura-ai/apis/kagura-memory-cloud/revisions/09f17f5ada29?raw)