sandboxes

Delete a snapshot; its stored-bytes meter stops (live forks keep running) [rate class: sandbox_api_rps]

Delete a snapshot and stop its stored-bytes meter. SCOPE: one image you baked, in your own workspace; live forks and everything outside the workspace are untouched. Snapshots bill for their deduplicated stored bytes for as long as they exist, so delete envs and checkpoints you are done forking - a finished batch usually ends with N delete_sandbox calls and one delete_sandbox_snapshot of the baked env. Deleting a snapshot never touches sandboxes already forked from it (they keep running and bill their own RAM-minutes until deleted); it only stops NEW forks, so take care of any fan-out you still want first. get_sandbox_stats lists your snapshots with their ids.

delete/preview/sandboxes/snapshots/{id}

Request

  • Base URL: https://autoresearch.sfcompute.com
  • URL: https://autoresearch.sfcompute.com/preview/sandboxes/snapshots/{id}
  • Auth: HTTP bearer

Path parameters

idstring required

The snapshot to delete: an env baked by create_sandbox_env, a state captured by snapshot_sandbox, or the snapshot a create_sandbox returned.

Query parameters

workspacestring

Act in this workspace (its slug). Omitted: the token's bound workspace, then the organization's default. Never ambient - there is no switch-workspace mutation on this door.

Response

The capability's JSON result.

objectstring

The resource type, when the result is one resource.

Changes

No recorded changes to this operation across all 1 revision of this API.