Request
Template to use. Either a system template (e.g., nodejs-20) or your custom template slug.
Persistent storage mounts. Each mount has workspaceId (your identifier) and path (mount location).
Seconds of inactivity before auto-pausing (default: 10 minutes). Set to 0 to disable auto-pause.
Resource limits for the sandbox.Show resources properties
Memory allocation (e.g., “2GB”, “4GB”, “8GB”)
Disk size (e.g., “10GB”, “50GB”, “100GB”)
Environment variables to set in the sandbox.
Custom metadata to attach to the sandbox.
Response
Unique sandbox identifier (e.g., sandbox-abc123)
Current status: creating, running, paused, stopped
Template used to create the sandbox
curl -X POST https://api.runtools.ai/v1/sandboxes \
-H "X-API-Key: rt_live_xxx" \
-H "Content-Type: application/json" \
-d '{
"template": "nodejs-20",
"mounts": [
{ "workspaceId": "my-project", "path": "/workspace" }
],
"idleTimeout": 600,
"resources": {
"vcpus": 2,
"memory": "4GB"
},
"env": {
"NODE_ENV": "development"
}
}'
{
"data": {
"id": "sandbox-abc123",
"status": "creating",
"template": "nodejs-20",
"resources": {
"vcpus": 2,
"memory": "4GB",
"disk": "10GB"
},
"createdAt": "2025-01-21T10:00:00Z"
}
}
Notes
- The sandbox starts in
creating status and transitions to running within ~2 seconds.
- Use Get Sandbox to check status.
- Billing starts when status is
running.