Sandboxes
Destroy a sandbox
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.
DELETE
Destroy a sandbox
Authorizations
Your account-level Brimble API key. Find it in the dashboard under your profile drawer → API key (click the avatar in the sidebar). Available on paid plans only.
Path Parameters
24-char hex id of the sandbox.
Pattern:
^[a-f0-9]{24}$Response
Destroy queued (or already destroyed)
Last modified on May 20, 2026
Previous
Pause a sandboxStops the sandbox's container while keeping its workspace volume (if any)
attached. Files under the sandbox's workspace directory survive; RAM state,
running processes, and open sockets do not.
Sandbox must be in status `ready`.
Async, the HTTP response acknowledges the request; `status` transitions
from `ready` to `paused` shortly after.
Next
Destroy a sandbox