# Delete sandbox

URL: https://docs.hanzo.ai/docs/openapi/sandbox/delete-sandbox-by-id

> Ends a sandbox and releases the compute behind it.

`DELETE /v1/sandbox/{id}`

> [Sandbox →](https://docs.hanzo.ai/docs/openapi/sandbox) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides)

|               |                                        |
| ------------- | -------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/sandbox/{id}` |
| **Method**    | `DELETE`                               |
| **Operation** | `delete_sandbox_by_id`                 |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY` |

Ends a sandbox and releases the compute behind it. Answers 204.

ENDING IS NOT STOPPING. This releases the resource: the pod goes and anything
only inside it goes with it. To end what a sandbox is RUNNING while keeping
the sandbox — the checkout, the logs, the half-written file — the verb is
POST /v1/sandbox/stop.

`?purge=1` additionally removes the record, so the sandbox stops being listed
at all rather than being listed as ended.

## Request

2 fields.

| Field   | In    | Type   | Required | Description                              |
| ------- | ----- | ------ | -------- | ---------------------------------------- |
| `id`    | path  | string | yes      | ID is the sandbox to end, from the path. |
| `purge` | query | string | —        |                                          |

## Response

| Status    | Body            | Meaning    |
| --------- | --------------- | ---------- |
| `204`     | —               | no content |
| `default` | problem-details | refused    |

Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors).

## Examples

**CLI**

```bash
hanzo sandbox rm <id>
```

**SDK**

**.ts**

```ts
import { Configuration, SandboxApi } from 'hanzoai';

const api = new SandboxApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteSandboxById({ id: 'id' });
```

**.py**

```python
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import SandboxApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SandboxApi(client).delete_sandbox_by_id(id='id')
```

**.go**

```go
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.SandboxAPI.DeleteSandboxById(context.Background()).Execute()
if err != nil {
	return err
}
```

**.rs**

```rust
use hanzo_client::apis::{configuration::Configuration, sandbox_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = sandbox_api::delete_sandbox_by_id(&cfg, Default::default()).await?;
```

**.java**

```java
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.SandboxApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new SandboxApi(client).deleteSandboxById();
```

**HTTP**

```bash
curl -X DELETE https://api.hanzo.ai/v1/sandbox/<id> \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **sandbox** through the `sandbox` tool, which names its 17 operations with its own verbs — this one among them, under a name only MCP declares. `describe` explains any of them:

```bash
curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_sandboxes"
         }
       }
     }'
```

---

[Sandbox API](https://docs.hanzo.ai/docs/openapi/sandbox) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)