# List files

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

> Lists one folder level of a drive.

`GET /v1/space/{space}/drives/{drive}/files`

> [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` |
| **Method**    | `GET`                                                        |
| **Operation** | `get_space_by_space_drives_by_drive_files`                   |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`                       |

Lists one folder level of a drive.

Folder-style by default: sub-folders come back as folder entries, which is the
file-manager view. `?recursive=true` lists every file flat under the folder
instead. Names are RELATIVE to `?folder=`, and the listing is bounded so a huge
drive cannot exhaust memory — Total is what came back, not what the drive holds.

Billed per call: the balance is checked BEFORE anything is touched, so an
unfunded org is refused with nothing read, and the debit lands only once the
listing has succeeded.

## Request

4 fields.

| Field       | In    | Type   | Required | Description                                   |
| ----------- | ----- | ------ | -------- | --------------------------------------------- |
| `space`     | path  | string | yes      | Space is the space to list in, from the path. |
| `drive`     | path  | string | yes      | Drive is the drive to list, from the path.    |
| `folder`    | query | string | —        |                                               |
| `recursive` | query | string | —        |                                               |

## Response

| Status    | Body            | Meaning |
| --------- | --------------- | ------- |
| `200`     | space.fileList  | ok      |
| `default` | problem-details | refused |

`200` body — 10 fields.

| Field                | In   | Type              | Always | Description                                                                                                                 |
| -------------------- | ---- | ----------------- | ------ | --------------------------------------------------------------------------------------------------------------------------- |
| `drive`              | body | string            | —      | Drive is the drive that was listed.                                                                                         |
| `files`              | body | space.fileItem\[] | —      | Files are the entries at this level, names RELATIVE to Folder.                                                              |
| `files[].etag`       | body | string            | —      | ETag is the store's entity tag for the bytes currently at this name, with the quotes the store wraps it in stripped.        |
| `files[].isFolder`   | body | boolean           | —      | Folder is true for a folder entry, which is emergent from "/" in the names beneath it rather than a thing that was created. |
| `files[].modifiedAt` | body | integer (int64)   | —      | ModifiedAt is when the file was last written, in unix seconds, and 0 for a folder.                                          |
| `files[].name`       | body | string            | —      | Name is the entry's name RELATIVE to the folder that was listed.                                                            |
| `files[].size`       | body | integer (int64)   | —      | Size is the file's size in bytes, and 0 for a folder.                                                                       |
| `folder`             | body | string            | —      | Folder is the sub-folder the listing was scoped to, cleaned.                                                                |
| `space`              | body | string            | —      | Space is the space that was listed.                                                                                         |
| `total`              | body | integer (int64)   | —      | Total is how many entries came back.                                                                                        |

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

## Examples

**CLI**

```bash
hanzo space drives files <space> <drive>
```

**SDK**

**.ts**

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

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

**.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).get_space_by_space_drives_by_drive_files(space='space', drive='drive')
```

**.go**

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

resp, _, err := client.SpaceAPI.GetSpaceBySpaceDrivesByDriveFiles(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::get_space_by_space_drives_by_drive_files(&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).getSpaceBySpaceDrivesByDriveFiles();
```

**HTTP**

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

**MCP**

MCP reaches **space** through the `space` tool, which names its 7 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)