Retrieve a sandbox
Poll this to follow provisioning and lifecycle changes. The platform does not send lifecycle webhooks.
Authorization
bearerAuth A RemoteHost API key (rh_sk_...) or a user session token.
In: header
Path Parameters
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/sandboxes/string"{ "sandbox": { "id": "string", "org_id": "string", "project_id": "string", "name": "string", "agent": "claude", "status": "provisioning", "mode": "persistent", "region": "string", "persistence_policy": "throwaway_ephemeral", "sandbox_profile": "string", "machine_size": "small", "provider": "string", "vmm": "string", "allocated_vcpu": 0, "allocated_memory_gb": 0, "allocated_disk_gb": 0, "end_user_id": "string", "vm_lost_at": "string", "environment_id": "string", "disk": { "usedBytes": 0, "totalBytes": 0, "availableBytes": 0, "warning": 80, "sampledAt": "string" }, "created_at": "string", "updated_at": "string" }}Resume a sandbox POST
Deprecated: use POST /sandboxes/{sandboxId}/wake.
Status of a sandbox's environment services GET
The services its environment declares, as this boot started them (where services are enabled; rolling out, and empty until then): after the setup script on a create or a cold boot, as the sandbox user, from /code or the service's cwd. A resume from memory keeps them running. A service that exits is not restarted. Empty when none were started this boot. The sandbox must be running or ready.