Manage running sandboxes with start, stop, TTL, snapshot, exec, logs, stats, file upload, and port exposure endpoints. Once a sandbox exists, the current api-server exposes a focused set of lifecycle endpoints.

​
Lifecycle Endpoints

CapabilityEndpoint
List sandboxesGET /sandboxes
Fetch one sandboxGET /sandboxes/{id}
Update metadata/configPUT /sandboxes/{id}
DeleteDELETE /sandboxes/{id}
StartPOST /sandboxes/{id}/start
StopPOST /sandboxes/{id}/stop
Extend TTLPOST /sandboxes/{id}/extend-ttl
Stop and snapshotPOST /sandboxes/{id}/stop-with-snapshot
Start from latest snapshotPOST /sandboxes/{id}/start-from-latest
Start from explicit snapshotPOST /sandboxes/{id}/start-from-snapshot
Execute commandPOST /sandboxes/{id}/exec
Upload filePOST /sandboxes/{id}/files
Read logsGET /sandboxes/{id}/logs
Read lifecycle-aware logsGET /sandboxes/{id}/logs/lifecycle
Read stats historyGET /sandboxes/{id}/stats/history
List portsGET /sandboxes/{id}/ports
Expose portsPOST /sandboxes/{id}/ports

​
Typical Flow

1

Create

Start with POST /sandboxes and capture the sandbox ID plus its workspace association.
2

Operate

Use exec, files, logs, and ports while the sandbox is running.
3

Pause Or Snapshot

Use stop, snapshots, or stop-with-snapshot depending on whether you need resumability.
4

Resume

Restart from the sandbox itself or from a recorded snapshot.

​
API Pages