---
title: "Forget an entire scope"
method: DELETE
path: "/v1/memory"
tags: ["Memory"]
---

# Forget an entire scope

`DELETE /v1/memory`

## Request

- Base URL: `https://api.zavu.dev`
- URL: `https://api.zavu.dev/v1/memory`
- Auth: HTTP bearer

Delete every fact in one scope. Returns immediately; the purge runs in batches in the background, so a list right afterwards can still show rows.

This does not touch collections — `DELETE /v1/memory/collections/{collection}` does that.

## Query parameters

- `scope` string: Scope as a query-string value: `contact:<contactId>`, `conversation:<conversationId>`, the literal `project`, or omitted for project scope. Only the SHAPE of the id is validated, never its existence — the partition already carries your project, so an id that matches nothing simply addresses an empty scope rather than returning 404.

## Response `202`

Purge scheduled.

- object
  - `status` string, required

## Other responses

- `400`: Invalid scope.
- `401`: Unauthorized.

## Changes

> 80 revisions in range; 1 not diffed.

- **2026-08-26** `6e8c555e1104`: 1 info
  - removed the non-success response with the status `403`
- **2026-08-26** `83caf7165722`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zavudev/apis/zavu-unified-messaging-layer-api/changes/v1/memory/delete.md)

---

[API](https://skmtc.dev/zavudev/apis/zavu-unified-messaging-layer-api.md) - [All operations](https://skmtc.dev/zavudev/apis/zavu-unified-messaging-layer-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zavudev/apis/zavu-unified-messaging-layer-api/revisions/75bc777b0ffb?raw)