Archive sandbox
Archives a sandbox. The changes its filesystem accumulated over its image are exported to the archive store, then the sandbox is shut down while its definition is kept, so it can be recreated later with the same disk. Memory and running processes are not preserved, processes are started again from their configuration when the sandbox is unarchived.
Authorizations
OAuth2 authentication with JWT tokens
Path Parameters
Name of the sandbox to archive
Response
Sandbox archived successfully
Lightweight virtual machine for secure AI code execution. Sandboxes resume from standby in under 25ms and automatically scale to zero after inactivity, preserving memory state including running processes and filesystem.
Common metadata fields shared by all Blaxel resources including name, labels, timestamps, and ownership information
Configuration for a sandbox including its image, memory, ports, region, and lifecycle policies
State of the filesystem archive of a sandbox. An archive holds the writable filesystem changes and the process configurations of the sandbox, not its memory, so restoring it produces a sandbox with the same disk state and freshly started processes.
Infrastructure failures recorded on the sandbox, oldest first (read-only, managed by the system)
Events happening on a resource deployed on Blaxel
Time in seconds until the sandbox is automatically deleted based on TTL and lifecycle policies. Only present for sandboxes with lifecycle configured.
Last time the sandbox was used (read-only, managed by the system)
Infrastructure generation this sandbox is deployed on (mk3.0 or mk3.1).
Current state of the sandbox (read-only, managed by the system)
RUNNING, STANDBY Deployment status of a resource deployed on Blaxel
DELETING, TERMINATED, FAILED, DEACTIVATED, DEACTIVATING, UPLOADING, BUILDING, DEPLOYING, DEPLOYED, BUILT, ARCHIVING, ARCHIVED, UNARCHIVING 