Skip to main content
Use this endpoint to pause a running capsule. Wrenn takes a full snapshot — VM state, memory, and filesystem — writes it to disk, then terminates the running Firecracker process and releases all host resources. The capsule persists as stored files and can be restored exactly to this point using the resume endpoint.
Pausing a capsule is the right choice when you want to stop incurring compute costs without losing the capsule’s in-memory state. Paused capsules consume only storage.

Endpoint

Authentication

Pass your API key in the X-API-Key header.

Path parameters

string
required
The ID of the capsule to pause (e.g., cl-abc123). The capsule must be in running status.

Response

Returns 200 OK with the updated capsule object. The status field will be "paused".
string
required
Unique capsule ID, prefixed with cl-.
string
required
Will be "paused" after a successful pause.
string
required
Name of the template the capsule was created from.
integer
required
Number of virtual CPUs that were allocated.
integer
required
Memory that was allocated, in MiB.
integer
required
Inactivity TTL in seconds.
string
required
ISO 8601 timestamp of when the capsule was created.
string
required
ISO 8601 timestamp of when the capsule was paused.

Example response

curl

Python SDK

Error responses