Skip to main content
POST
Archive sandbox

Authorizations

Authorization
string
header
required

OAuth2 authentication with JWT tokens

Path Parameters

sandboxName
string
required

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.

metadata
object
required

Common metadata fields shared by all Blaxel resources including name, labels, timestamps, and ownership information

spec
object
required

Configuration for a sandbox including its image, memory, ports, region, and lifecycle policies

archive
object

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.

errors
object[]
read-only

Infrastructure failures recorded on the sandbox, oldest first (read-only, managed by the system)

events
object[]
read-only

Events happening on a resource deployed on Blaxel

expiresIn
integer
read-only

Time in seconds until the sandbox is automatically deleted based on TTL and lifecycle policies. Only present for sandboxes with lifecycle configured.

lastUsedAt
string
read-only

Last time the sandbox was used (read-only, managed by the system)

nodeGeneration
string
read-only

Infrastructure generation this sandbox is deployed on (mk3.0 or mk3.1).

state
enum<string>
read-only

Current state of the sandbox (read-only, managed by the system)

Available options:
RUNNING,
STANDBY
status
enum<string>
read-only

Deployment status of a resource deployed on Blaxel

Available options:
DELETING,
TERMINATED,
FAILED,
DEACTIVATED,
DEACTIVATING,
UPLOADING,
BUILDING,
DEPLOYING,
DEPLOYED,
BUILT,
ARCHIVING,
ARCHIVED,
UNARCHIVING
Last modified on August 26, 2026