---
title: "Restore a deleted diagram"
method: POST
path: "/v1/diagrams/{id}/undelete"
tags: ["Diagrams"]
---

# Restore a deleted diagram

`POST /v1/diagrams/{id}/undelete`

## Request

- Base URL: `https://api.zindex.ai`
- URL: `https://api.zindex.ai/v1/diagrams/{id}/undelete`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Within 24 hours of deleting. If another diagram took its key meanwhile, it comes back without a key and says so.

## Path parameters

- `id` string, required

## Response `200`

{ id, restored: true, revision, key, note? }

## Other responses

- `401`: Missing or invalid API key. Response includes a `code` field that distinguishes the failure mode so clients (dashboard, MCP server) can render actionable copy: `AUTH_REQUIRED` (no key or session was sent), `API_KEY_INVALID` (key not found), `API_KEY_REVOKED` (key was revoked, or its person is no longer in its workspace), `API_KEY_EXPIRED` (key passed its expires_at), and for the site's session cookie `SESSION_EXPIRED` (past its 24 hours), `SESSION_REVOKED` (the account's sessions were ended, for example by a password reset) and `SESSION_INVALID` (not a session this server signed).
- `403`: LIMIT_REACHED: the workspace is at its diagram limit (scenes), which a restore counts against as a create does; EMAIL_NOT_VERIFIED: verify the account's email first; READ_ONLY: a read key or a viewer. Nothing was restored
- `404`: NOT_FOUND: nothing restorable
- `429`: RATE_LIMITED: over the request rate limit (see Rate Limiting). Wait retryAfter seconds (also the Retry-After header), then try again.

## Changes

- **2026-10-20** `1d21bd5bbf8e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zindex/apis/zindex-api/changes/v1/diagrams/:id/undelete/post.md)

---

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