---
title: "Discard Brain Dump"
method: DELETE
path: "/api/onboarding/brain-dump"
tags: ["v1", "onboarding", "onboarding", "brain-dump"]
---

# Discard Brain Dump

`DELETE /api/onboarding/brain-dump`

Drop a half-uploaded take's server buffer when the user re-records.

The row and any stored audio are left alone — only the disposable
part buffer is cleared.

``recording_id`` says *which* take to drop. Without it the row's
current take is assumed, which is wrong as soon as a second tab has
moved the row on: the caller would clear a buffer that is still being
filled. Callers know their own id, so they send it.

## Query parameters

- `recording_id` string, nullable

## Response `200`

Successful Response

- DumpStatusResponse
  - `status` 'recording_uploaded' | 'transcribing' | 'transcribed' | 'extracting' | 'completed' | 'failed'
  - `input_mode` 'voice' | 'typed' | 'skipped'
  - `error_code` string, nullable
  - `has_audio` boolean
  - `greeting_ready` boolean

## Other responses

- `401` — Authentication required
- `422` — Validation Error

---

[API](https://skmtc.net/significant-gravitas/apis/autogpt-agent-server.md) · [All operations](https://skmtc.net/significant-gravitas/apis/autogpt-agent-server/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/significant-gravitas/autogpt-agent-server/versions/382041c7ecb2/schema)