---
title: "Whether a memory-evolution auto-archive can still be undone"
method: GET
path: "/api/contexts/{id}/undo-archive-info"
tags: ["Contexts"]
---

# Whether a memory-evolution auto-archive can still be undone

`GET /api/contexts/{id}/undo-archive-info`

## Request

- Base URL: `http://localhost:38200`
- URL: `http://localhost:38200/api/contexts/{id}/undo-archive-info`
- Auth: one of:
  - HTTP bearer
  - API key in cookie `token`

Only archives performed by memory_evolution_archive are undoable — a manual PUT lifecycle=archived does not qualify.

## Path parameters

- `id` integer, required

## Response `200`

Always 200 — `undoable:false` carries the reason via the other fields.

- object
  - `undoable` boolean
  - `archived_at` string, date-time, nullable
  - `window_hours` integer
  - `expires_at` string, date-time, nullable

## Other responses

- `400`: Invalid id.
- `401`: Missing or invalid credentials.
- `404`: Resource not found (or not visible to the caller).

---

[API](https://skmtc.dev/contextq/apis/contextq-api.md) · [All operations](https://skmtc.dev/contextq/apis/contextq-api/llms.txt) · [OpenAPI document](https://skmtc.dev/contextq/apis/contextq-api/revisions/7afc44056a22?raw)