# List files

URL: https://docs.hanzo.ai/docs/openapi/git/get-git-repos-by-name-files

> Returns every file a glob selects at one revision, WITH its bytes and the revision they came from.

`GET /v1/git/repos/{name}/files`

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

|               |                                                  |
| ------------- | ------------------------------------------------ |
| **Address**   | `https://api.hanzo.ai/v1/git/repos/{name}/files` |
| **Method**    | `GET`                                            |
| **Operation** | `get_git_repos_by_name_files`                    |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY`           |

Returns every file a glob selects at one revision, WITH its bytes
and the revision they came from. It is the read a delivery generator makes:
one call answers "what is the inventory at this commit, and what does it say",
where listing and then fetching would be a request per file.

Returning the resolved revision matters as much as the bytes. A generator that
lists at `main` and then reads at `main` can straddle a push and assemble half
its inventory from one commit and half from the next; resolving once makes the
whole read consistent by construction.

A file past the read cap comes back Truncated with no content rather than
being dropped. A caller building a desired set has to know the difference
between "this file is empty" and "this file was not read" — silently omitting
it is how a pruning reconcile deletes what the missing file declared.

## Request

3 fields.

| Field  | In    | Type   | Required | Description                                                                |
| ------ | ----- | ------ | -------- | -------------------------------------------------------------------------- |
| `name` | path  | string | yes      | Name is the repo to read, from the :name path segment.                     |
| `ref`  | query | string | —        | Ref is a branch, tag or commit; empty means the repo's HEAD.               |
| `glob` | query | string | —        | Glob selects files, matched segment by segment so `*` never crosses a `/`. |

## Response

| Status    | Body            | Meaning |
| --------- | --------------- | ------- |
| `200`     | git.filesJSON   | ok      |
| `default` | problem-details | refused |

`200` body — 7 fields.

| Field               | In   | Type            | Always | Description                                                               |
| ------------------- | ---- | --------------- | ------ | ------------------------------------------------------------------------- |
| `files`             | body | git.fileJSON\[] | —      | Files are the selected files, sorted by path.                             |
| `files[].content`   | body | string          | —      | Content is the file's bytes, empty when Truncated.                        |
| `files[].encoding`  | body | string          | —      | Encoding is how Content is carried: "utf8" verbatim, or "base64".         |
| `files[].path`      | body | string          | —      | Path is the file's repo-relative path.                                    |
| `files[].size`      | body | integer (int64) | —      | Size is the file's byte length in the repo.                               |
| `files[].truncated` | body | boolean         | —      | Truncated marks a file past the read cap; no content is sent.             |
| `rev`               | body | string          | —      | Rev is the full revision the ref resolved to — pin follow-up reads to it. |

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

## Examples

**CLI**

```bash
hanzo git repos files <name>
```

**SDK**

**.ts**

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

const api = new GitApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getGitReposByNameFiles({ name: 'name' });
```

**.py**

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = GitApi(client).get_git_repos_by_name_files(name='name')
```

**.go**

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

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

**.rs**

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

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

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

**.java**

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

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

var result = new GitApi(client).getGitReposByNameFiles();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/git/repos/<name>/files \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

MCP reaches **git** through the `git` tool, which names its 38 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_git_keys"
         }
       }
     }'
```

---

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