---
title: "Destroy a sandbox"
method: DELETE
path: "/sandboxes/{id}"
tags: ["Sandboxes"]
---

# Destroy a sandbox

`DELETE /sandboxes/{id}`

Tears down the sandbox immediately. The HTTP response is `204` once the
destroy is queued; the sandbox's `status` transitions to `destroyed`
shortly after.

Idempotent, calling DELETE on an already-destroyed sandbox is a no-op
that still returns `204`.

Attached volumes are detached but **not** deleted; they can be re-attached
to a future sandbox.

## Path parameters

- `id` string, required

## Response `204`

Destroy queued (or already destroyed)

## Other responses

- `400` — Validation error / invalid state transition
- `404` — Sandbox or related resource not found (also returned when owned by another user)

---

[API](https://skmtc.net/brimblehq/apis/brimble-sandbox-api.md) · [All operations](https://skmtc.net/brimblehq/apis/brimble-sandbox-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/brimblehq/brimble-sandbox-api/versions/7fe2df041597/schema)