---
title: "Delete Memories Bulk"
method: DELETE
path: "/memories"
tags: ["Memories"]
---

# Delete Memories Bulk

`DELETE /memories`

## Request

- Base URL: `https://api.getmetacognition.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.getmetacognition.com/memories`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/metacognition/apis/tex-api/docs/memories/delete.ts> (a function with typed inputs; its response is checked against the schema)

Erase a user's personal memories (GDPR/CCPA erasure) from every store.

The same erasure as the deletion API's ``user_scope`` target, and audited
the same way (a deletion request + receipt, purged after the retention
window): every node in the user's personal scope (and their unstamped
legacy nodes), the vectors stamped with it in every namespace, their
personal active-tier fragments, turn index rows and edit history. This
route used to tombstone engine nodes only — the active copies kept
answering recall and inferences kept answering NLQ — and answered 500 on
the first node it could see but not delete. ``deleted_count`` is engine
nodes tombstoned.

## Query parameters

- `user_id` string, nullable: Target user_id to erase. If omitted, deletes the caller's own memories. Only admin/developer may erase other users.

## Response `200`

Successful Response

- MemoryBulkDeleteResponse: Response from bulk memory deletion (GDPR/CCPA erasure).
  - `success` boolean, required: Whether deletion succeeded
  - `deleted_count` integer, required: Number of memories soft-deleted
  - `user_id` string, required: User ID whose memories were deleted
  - `message` string: Status message

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/metacognition/apis/tex-api.md) - [All operations](https://skmtc.dev/metacognition/apis/tex-api/llms.txt) - [OpenAPI document](https://skmtc.dev/metacognition/apis/tex-api/revisions/3bef47e50f2e?raw)