Stop a sandbox
Stop a running sandbox while preserving its writable disk changes. The sandbox transitions through `stopping` to `stopped`. Unlike pause, stop does not preserve in-memory execution state.
Stop a running sandbox while preserving its writable disk changes. The sandbox
transitions through stopping to stopped. Unlike pause, stop does not
preserve in-memory execution state.
Authorization
BearerAuth API key passed as a Bearer token in the Authorization header.
Alternatively, use the leap0-authorization header.
In: header
Path Parameters
Unique sandbox identifier.
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://api.leap0.dev/v1/sandbox/string/stop"{ "id": "sbx-abc123", "template_id": "string", "mounts": [ { "id": "mnt-abc123", "type": "object-storage", "bucket": "string", "mount_path": "string", "prefix": "string", "read_only": true } ], "vcpu": 1, "memory": 1, "disk": 1, "timeout": 1, "state": "starting", "auto_pause": true, "network_policy": { "mode": "allow-all", "allow_domains": [ "string" ], "allow_cidrs": [ "string" ], "transforms": [ { "domain": "string", "inject_headers": { "property1": "string", "property2": "string" }, "strip_headers": [ "string" ] } ] }, "created_at": "2019-08-24T14:15:22Z"}{ "message": "string"}{ "message": "string"}{ "message": "string"}Pause a sandbox POST
Pause a running sandbox. The sandbox's VM state, memory, and disk are captured and uploaded, the sandbox is marked as paused, and the VM is terminated. The sandbox can later be resumed via the invoke route or the resume endpoint, which restores it from the saved state. Unlike `POST /snapshot/create` with `kill_sandbox_after`, this does **not** create a named snapshot.
Start a stopped sandbox POST
Start a sandbox that is currently `stopped`. Leap0 boots a fresh VM from the original template and reapplies the persisted writable disk diff before the sandbox returns to `running`.