Create sandbox (v2)
Create a sandbox from the template. All system communication with the sandbox is secured.
Anona: size (small, medium, large or xl) sets the sandbox’s vCPU, memory and disk; an E2B SDK can send it as metadata anona.size instead. Without it the sandbox runs at its template’s own size, or on Free at the smallest size the template allows (Small for base). A size below the template’s minimum is 400 sandbox_size_not_available, and one above your plan’s largest size is 403 plan_limit_exceeded; the first sandbox at a size the template was not built at may get 503 sandbox_size_preparing with Retry-After while that size is prepared (see Sandbox sizes). Over a plan limit on what runs at once (sandboxes, vCPU, or sandboxes at the largest size) is 429 plan_limit_exceeded with limit_name, limit, current and plan. timeout also accepts -1 for no deadline. lifecycle.onTimeout: pause (sent by the SDK as autoPause) pauses instead of deleting. A sandbox without a deadline reports endAt 9999-12-31T23:59:59Z. network.egressProxy, volumeMounts, iam and autoPauseMemory: false are refused with 400, and the Idempotency-Key header is not supported.
Body
Sandbox creation request. All system communication with the sandbox is always secured; the template's envd version must support secured access.
Controls the snapshot kind taken when the sandbox auto-pauses on timeout (only relevant when autoPause is true). When false, the auto-pause drops the in-memory state and persists only the filesystem (a filesystem-only snapshot); resuming it cold-boots (reboots) the sandbox from disk. Such a snapshot cannot be auto-resumed by traffic and must be resumed explicitly, so it cannot be combined with autoResume. Defaults to true (full memory snapshot).
Response
The sandbox was created successfully