Kill Sandbox

​

Endpoint

POST /v1/sandboxes/:id/kill

​

Request

​

Headers

Authorization: Bearer $HOPX_API_KEY

​

Path Parameters

​

Example Request

curl -X POST https://api.hopx.dev/v1/sandboxes/sandbox_abc123xyz/kill \
  -H "Authorization: Bearer $HOPX_API_KEY"

​

Response

​

Success (200 OK)

{
  "id": "sandbox_abc123xyz",
  "status": "killed",
  "request_id": "req_abc123"
}

​

Response Fields

​

Status Codes

​

Errors

​

Sandbox Not Found (404)

{
  "error": "Sandbox not found",
  "code": "RESOURCE_NOT_FOUND",
  "request_id": "req_abc123"
}

​

Important Notes

• 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

​

Use Cases

​

Kill Unresponsive Sandbox

# Kill a sandbox that's not responding
curl -X POST https://api.hopx.dev/v1/sandboxes/sandbox_abc123xyz/kill \
  -H "Authorization: Bearer $HOPX_API_KEY"

​

Force Cleanup

# Kill instead of delete when sandbox is stuck
curl -X POST https://api.hopx.dev/v1/sandboxes/sandbox_abc123xyz/kill \
  -H "Authorization: Bearer $HOPX_API_KEY"

​

Difference from Delete

• Kill - Forcefully terminates the sandbox immediately, even if unresponsive
• Delete - Gracefully deletes the sandbox (may fail if sandbox is stuck)

​

Related

• Managing Sandbox State - Learn about sandbox lifecycle
• Delete Sandbox - Gracefully delete a sandbox
• Stop Sandbox - Stop instead of killing
• SDK: sandbox.kill() - Python SDK method
• CLI Sandbox Commands - Manage sandboxes from CLI

​

Next Steps

• Delete Sandbox - Gracefully delete a sandbox
• Stop Sandbox - Stop instead of killing
• Get Sandbox - Check sandbox status