---
title: "Restore a soft-deleted vault"
method: POST
path: "/api/vaults/{id}/restore"
tags: ["Vaults"]
---

# Restore a soft-deleted vault

`POST /api/vaults/{id}/restore`

## Request

- Base URL: `https://api.engram.page`
- URL: `https://api.engram.page/api/vaults/{id}/restore`
- Auth: HTTP bearer

Restores a soft-deleted vault back to active within its 30-day window. Returns 402 when restoring would exceed the plan's vault cap and 404 when no such vault exists.

## Path parameters

- `id` string, required

## Response `200`

Restored

- VaultResponse
  - `vault` Vault, required
    - `attachment_count` integer
    - `created_at` string, date-time, nullable
    - `deleted_at` string, date-time, nullable
    - `encrypted` boolean: Always true — vaults are encrypted at rest.
    - `id` string, uuid, required
    - `is_default` boolean
    - `name` string, required
    - `note_count` integer
    - `populated` boolean: True once the vault holds a note other than the seeded welcome note (the moment the `vault_populated` event fires).
    - `purge_at` string, date-time, nullable: When a soft-deleted vault is hard-purged (deleted_at + 30d).
    - `slug` string, nullable

## Other responses

- `402`: Vault cap reached
- `403`: The credential may not restore this vault: this needs write access to it
- `404`: No such vault, or one the credential cannot reach (the two look the same)

---

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