---
title: "Restore Memory"
method: POST
path: "/v1/memories/restore"
tags: ["memories"]
---

# Restore Memory

`POST /v1/memories/restore`

## Request

- Base URL: `https://api.heirmos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.heirmos.com/v1/memories/restore`
- Auth: HTTP bearer

복구 — un-archive the latest archived memory at ``body.path`` (SPEC §14.9
soft-delete is reversible). 404 if nothing archived there; PATH_CONFLICT if a
current memory already occupies the path.

## Request body

- RestoreRequest: POST /v1/memories/restore — un-archive (복구) the latest archived memory at ``path``. Only valid when no current memory occupies the path.
  - `path` string, required

## Response `200`

Successful Response

- MemoryRead: GET /v1/memories/{path:path} response — SPEC §5.3 line 326-339. `summary` is included even though SPEC's example omits it: the column exists (SPEC §4.1) and list responses surface it, so a single-memory read should too.
  - `id` string, uuid, required
  - `path` string, required
  - `title` string, nullable
  - `content` string, required
  - `summary` string, nullable
  - `tags` string[], required
  - `importance` number, required
  - `source` string, required
  - `version` integer, required
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required
  - `type` string, nullable
  - `scope` string, nullable
  - `status` string
  - `confidence` number, nullable
  - `privacy_sensitivity` number, nullable
  - `secondary_folders` string[]
  - `source_kind` string, nullable
  - `source_id` string, nullable
  - `evidence_quote` string, nullable
  - `ai_reasoning_summary` string, nullable
  - `valid_from` string, date-time, nullable
  - `valid_until` string, date-time, nullable
  - `occurred_at` string, date-time, nullable
  - `summary_for_ai` string, nullable
  - `retrieval_keywords` string[], nullable
  - `embedding_text` string, nullable
  - `folder_context` string, nullable
  - `related_memory_ids` string[], nullable
  - `dedup` DedupInfo: Advisory write-time dedup result — Phase 13 P13-2 (SPEC §10 + §15 #17). Rides on the ``POST /v1/memories`` response body **only** (never persisted). The server always saves the memory (201); this tells the client/user that the new memory resembles an existing one so they can choose to merge into ``suggested_path``. Propose-only — the server never blocks or auto-mutates.
    - `relation` 'same' | 'similar' | 'related' | 'conflicting' | 'new', required
    - `suggested_path` string, nullable
    - `rationale` string
    - `similarity` number, nullable

## Other responses

- `422`: Validation Error

---

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