Forcefully terminate a sandbox immediately using the HopX Control Plane API. Immediately stop a sandbox and free all resources without waiting for graceful shutdown. Learn how to use POST /v1/sandboxes/:id/kill endpoint to force-terminate sandboxes. Includes request examples and termination behavior.
Kill a sandbox to forcefully terminate it immediately. This is similar to delete but may be used when a sandbox is unresponsive. The sandbox is destroyed and cannot be recovered.
{ "error": "Sandbox not found", "code": "RESOURCE_NOT_FOUND", "request_id": "req_abc123"}
Cause: The sandbox ID doesn’t exist or belongs to another organization.Fix: Verify the sandbox ID is correct. List your sandboxes using GET /v1/sandboxes to find valid IDs.
Killing a sandbox is permanent and irreversible. All data, files, and state in the sandbox will be lost. This action forcefully terminates the sandbox even if it’s unresponsive.
Immediate termination - The sandbox is forcefully terminated immediately
No graceful shutdown - Running processes are killed without cleanup
Resource cleanup - All allocated resources are freed
VM Agent API - The sandbox’s VM Agent API endpoint becomes unavailable immediately
No recovery - Killed sandboxes cannot be recovered
# Kill instead of delete when sandbox is stuckcurl -X POST https://api.hopx.dev/v1/sandboxes/sandbox_abc123xyz/kill \ -H "Authorization: Bearer $HOPX_API_KEY"
