# Delete files

URL: https://docs.hanzo.ai/docs/openapi/space/delete-space-by-space-drives-by-drive-files-by-wildcard1

> Removes one file and answers 204.

`DELETE /v1/space/{space}/drives/{drive}/files/{wildcard1}`

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

|               |                                                                          |
| ------------- | ------------------------------------------------------------------------ |
| **Address**   | `https://api.hanzo.ai/v1/space/{space}/drives/{drive}/files/{wildcard1}` |
| **Method**    | `DELETE`                                                                 |
| **Operation** | `delete_space_by_space_drives_by_drive_files_by_wildcard1`               |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`                                   |

Removes one file and answers 204.

It removes ONE file and never a folder: a name that looks like a folder is
refused, because a folder is emergent from the names beneath it and deleting
one would have to mean deleting them. The name is path-cleaned first, so the
delete cannot reach outside the drive it names, and a space the caller's org
does not own is the same 404 an unknown name gives.

Billed per call: the balance is checked BEFORE anything is touched, so an
unfunded org is refused with nothing deleted, and the debit lands only once the
file is gone.

## Request

3 fields.

| Field       | In   | Type   | Required | Description                                                                       |
| ----------- | ---- | ------ | -------- | --------------------------------------------------------------------------------- |
| `space`     | path | string | yes      | Space is the space's name, from the path.                                         |
| `drive`     | path | string | yes      | Drive is the drive's name, from the path.                                         |
| `wildcard1` | path | string | yes      | File is the file's name within the drive — everything after that drive's /files/. |

## 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 space drives files rm <space> <drive> <wildcard1>
```

**SDK**

**.ts**

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

const api = new SpaceApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteSpaceBySpaceDrivesByDriveFilesByWildcard1({ space: 'space', drive: 'drive', wildcard1: 'wildcard1' });
```

**.py**

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SpaceApi(client).delete_space_by_space_drives_by_drive_files_by_wildcard1(space='space', drive='drive', wildcard1='wildcard1')
```

**.go**

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

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

**.rs**

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

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

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

**.java**

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

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

var result = new SpaceApi(client).deleteSpaceBySpaceDrivesByDriveFilesByWildcard1();
```

The method above is the one at the current release of the document. `hanzoai@8.5.914` (npm) and `hanzoai@8.5.914` (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. [SDKs →](https://docs.hanzo.ai/docs/sdks)

**HTTP**

```bash
curl -X DELETE https://api.hanzo.ai/v1/space/<space>/drives/<drive>/files/<wildcard1> \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **space** through the `space` tool, which names its 10 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_space_drives"
         }
       }
     }'
```

---

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