List comments

One issue's conversation, oldest first, read as the caller.

GET /v1/task/projects/{key}/issues/{num}/comments

Task → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/task/projects/{key}/issues/{num}/comments`
Method	`GET`
Operation	`get_task_projects_by_key_issues_by_num_comments`
Auth	`Authorization: Bearer $HANZO_API_KEY`

One issue's conversation, oldest first, read as the caller. An issue that lives on GitHub names its home and is read there.

Request

2 fields.

Field	In	Type	Required	Description
`key`	path	string	yes	Key is the board — the repository name, or an index board's key.
`num`	path	integer	yes	Num is the issue's number on that board.

Response

Status	Body	Meaning
`200`	task.commentList	ok
`default`	problem-details	refused

200 body — 6 fields.

Field	In	Type	Always	Description
`data`	body	task.comment[]	—	Data is the conversation.
`data[].author`	body	string	—	Author is who wrote it: their name, else their forge login.
`data[].body`	body	string	—	Body is what was written, as markdown.
`data[].createdAt`	body	string	—	CreatedAt is when it was written, RFC 3339.
`data[].id`	body	integer (int64)	—	ID is the forge's id for the comment.
`home`	body	string	—	Home is the GitHub repository (owner/name) the issue lives on when its board mirrors one; its conversation is read there, and Data is then empty.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

.ts

.py

.go

.rs

.java

import { Configuration, TaskApi } from 'hanzoai';

const api = new TaskApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTaskProjectsByKeyIssuesByNumComments({ key: 'key', num: 'num' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TaskApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TaskApi(client).get_task_projects_by_key_issues_by_num_comments(key='key', num='num')

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

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

use hanzo_client::apis::{configuration::Configuration, task_api};

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

let result = task_api::get_task_projects_by_key_issues_by_num_comments(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TaskApi;

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

var result = new TaskApi(client).getTaskProjectsByKeyIssuesByNumComments();

curl https://api.hanzo.ai/v1/task/projects/<key>/issues/1/comments \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches task through the task 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:

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": "get_task_board"
         }
       }
     }'

Task API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList issues — GET /v1/task/issues NextGet issues