List refs — GET /v1/git/repos/{name}/refs

Lists a repo's branches, tags and default branch — what a branch picker needs in one call.

GET /v1/git/repos/{name}/refs

Git → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/git/repos/{name}/refs`
Method	`GET`
Operation	`get_git_repos_by_name_refs`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists a repo's branches, tags and default branch — what a branch picker needs in one call. Unlike the other read ops it tolerates a repo with no commits: the ref sets come back empty and the default branch is still named.

Request

1 field.

Field	In	Type	Required	Description
`name`	path	string	yes	Name is the repo's org-unique handle, from the :name path segment.

Response

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

200 body — 7 fields.

Field	In	Type	Always	Description
`branches`	body	git.refJSON[]	—	Branches are the repo's heads; empty on a repo with no commits.
`branches[].name`	body	string	—	Name is the short ref name ("main", "v1.2.0"), not the full refs/… path.
`branches[].sha`	body	string	—	SHA is the full commit hash the ref resolves to.
`default`	body	string	—	Default is the branch name a caller gets when it asks for no ref.
`tags`	body	git.refJSON[]	—	Tags are the repo's tags; empty when there are none.
`tags[].name`	body	string	—	Name is the short ref name ("main", "v1.2.0"), not the full refs/… path.
`tags[].sha`	body	string	—	SHA is the full commit hash the ref resolves to.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo git repos refs <name>

.ts

.py

.go

.rs

.java

import { Configuration, GitApi } from 'hanzoai';

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

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_refs(name='name')

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

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

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_refs(&cfg, Default::default()).await?;

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).getGitReposByNameRefs();

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

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:

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 · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList readme NextList subscriptions