Pause a running sandbox
Snapshots the sandbox’s full state (memory + disk), suspends the VM,
and transitions to paused. Resume it later to continue exactly where
it left off — same memory, same running processes, same files.
The request holds until the pause is decided; if the host has not
answered by then, the response is 202 Accepted and the pause
continues in the background. Send Prefer: respond-async to get
202 as soon as the pause is recorded instead. Either way
GET /sandboxes/{sandbox_id} reports paused once it lands (or
failed if the VM turned out to be gone).
Authorizations
Headers
Accept 202 with {"status":"pausing"} over a held connection.
respond-async Path Parameters
The unique identifier of the sandbox.
Public sandbox ID: a bare UUID, or the region-tagged form sb-<region>-<uuid> (e.g. sb-use-1b4e28ba-…). Treat as an opaque string; the tagged form routes the request to the sandbox's home region. Endpoints accept both forms interchangeably.
^(sb-[a-z0-9]+-)?[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$Response
Pause recorded and in progress; poll the sandbox until it is paused. Immediate with Prefer: respond-async, otherwise returned when the pause is still in progress after the request's wait.
pausing