# Forget an entire scope

> 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.

`DELETE https://api.zavu.dev/v1/memory`

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.

## Parameters

- `scope` (query, string): Which scope to address: `contact:<contactId>`, `conversation:<conversationId>`, or omitted for the project scope. Note the asymmetry with `POST /v1/memory` and `POST /v1/memory/search`, which take the scope in the request BODY as `scope` plus `contactId`/`conversationId`. Every other Memory endpoint takes it here.

## Responses

### 202

Purge scheduled.

- `status` (string, required)

### 400

Invalid scope.

- `code` (string, required)
- `message` (string, required)
- `details` (object)

### 401

Unauthorized.

- `code` (string, required)
- `message` (string, required)
- `details` (object)

## Example

```bash
curl -X DELETE "https://api.zavu.dev/v1/memory" \
  -H "Authorization: Bearer $ZAVUDEV_API_KEY"
```

```typescript
import Zavudev from "@zavudev/sdk";

const zavu = new Zavudev({ apiKey: process.env.ZAVUDEV_API_KEY });

const result = await zavu.memory.wipe();

console.log(result);
```