---
title: "Delete an engram"
method: DELETE
path: "/v1/memories/{id}"
tags: ["Memories"]
---

# Delete an engram

`DELETE /v1/memories/{id}`

Delete a specific engram with graph awareness. All chunks corresponding to the
engram are deleted, and graph components (entities/relationships) are updated
or deleted based on remaining chunk references from other engrams.

This method now properly handles graph components and maintains graph integrity
for search operations.

## Path parameters

- `id` string, uuid, required — Engram ID

## Response `200`

Successful Response

- NebulaResultsGenericBooleanResponse
  - `results` GenericBooleanResponse, required
    - `success` boolean, required

## Other responses

- `422` — Validation Error

## Changes

- **2026-04-27** `b1da2c0bb1ae` — 4 info
  - api operation id `delete_engram_by_id_v1_memories__id__delete` removed and replaced with `delete_memory`
  - api tag `Memories` added
  - added the optional property `detail/items/ctx` to the response with the `422` status
  - added the optional property `detail/items/input` to the response with the `422` status

[Change history](https://skmtc.dev/zeroset-inc/apis/nebula-api/changes/v1/memories/:id/delete.md)

---

[API](https://skmtc.dev/zeroset-inc/apis/nebula-api.md) · [All operations](https://skmtc.dev/zeroset-inc/apis/nebula-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/zeroset-inc/nebula-api/revisions/b1da2c0bb1ae/schema)