Changelog

Public API 0.8.0: manual backups and asynchronous backup deletion

Start a backup immediately with POST /compute/cloud-vms/{vm_id}/backups/runs or POST /compute/gpu-vms/{vm_id}/backups/runs. An enabled backup policy is required. Send {"requested_by":"api"} to use that policy’s stored billing catalog, or supply an explicit billing_catalog override. The response includes the queued run_id; poll the run until it succeeds or fails. Both operations require vm.write and a workspace_id query parameter.

Deleting a completed backup now returns 202 with status: deleting. The run remains readable while remote cleanup runs, then GET returns 404. A subsequent DELETE also returns 404. Dependency and active-restore conflicts still return 409.