Sandboxes
Pause a sandbox
Stops 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.
POST
Pause 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
Pause queued
Example:
"Sandbox pause requested"
Last modified on May 20, 2026
Previous
Resume a paused sandboxStarts a fresh container of the same template and reattaches the persistent
volume. Files under the sandbox's workspace directory come back; nothing else
does.
Sandbox must be in status `paused`. `status` transitions from `paused` to
`ready` once the container is up.
Next
Pause a sandbox