List issues — GET /v1/task/projects/{key}/issues

Returns a board's issues — work items with their column, priority, assignee, labels and schedule.

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

Task → · All API references → · Get started →

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

Returns a board's issues — work items with their column, priority, assignee, labels and schedule.

WHICH board is a filter, not an address. Bound to a repository (the key from the path) it is that project's board; left unbound it is the org's whole board; narrowed by label it is a board smaller than any repository — which is the only way an app that lives as a directory inside a shared repository can have one. Every combination is the same rows through the same projection, so no two boards can disagree about what a column means.

The column is a LABEL on the forge, so the board and the forge web UI are the same object seen twice: relabelling in either moves the card in both. A closed issue reads as done whatever its labels say.

Request

7 fields.

Field	In	Type	Required	Description
`key`	path	string	yes	Key is the project whose issues to list, from the path.
`status`	query	string	—	Status keeps only issues in that board column: backlog, todo, in_progress, done or canceled.
`kind`	query	string	—	Kind keeps only work items of that shape: issue, pr or epic.
`repo`	query	string	—	Repo keeps only issues bound to that git repository.
`label`	query	string	—	Label keeps only issues carrying that label, compared case-insensitively.
`source`	query	string	—	Source keeps only issues opened from that surface: team, git, crm, helpdesk, cms or agent.
`scheduled`	query	boolean	—	Scheduled keeps only issues that carry a date — a start, a due date or both.

Response

Status	Body	Meaning
`200`	task.issueView[]	ok
`default`	problem-details	refused

200 body — 19 fields.

Field	In	Type	Always	Description
`[].assignee`	body	string	—	Assignee is who holds the work — an IAM username, or the login of the FIRST assignee when a forge issue has several.
`[].createdAt`	body	integer (int64)	—	CreatedAt is when the item was opened, in unix seconds.
`[].description`	body	string	—	Description is the body, markdown as its author wrote it.
`[].dueAt`	body	integer (int64)	—	DueAt is when the work is due, in unix seconds; absent means no due date.
`[].extRef`	body	string	—	ExtRef anchors the item to something outside the task — a mirrored issue ("github:owner/repo#123"), a pushed PR branch, or a record on another plane.
`[].id`	body	string	—	ID is the work item's opaque handle, and it is NOT how you address it — ProjectKey plus Number is.
`[].identifier`	body	string	—	Identifier is the human handle, "<key>#<number>" — the board and the number on it, joined.
`[].kind`	body	string	—	Kind is what the item IS: issue, pr or epic.
`[].labels`	body	string[]	—	Labels are the item's remaining tags, with the status and priority labels lifted OUT — a column that stayed here would render twice, once as the card's column and once as a chip on the card.
`[].number`	body	integer (int64)	—	Number is the item's number ON ITS BOARD, from 1 and monotonic there — the forge's own issue number for a forge row, allocated inside the create transaction for an index row so it cannot race.
`[].priority`	body	string	—	Priority is urgent, high, medium, low or none.
`[].projectKey`	body	string	—	ProjectKey is the board this item is on: the repository name for a forge issue, the index board's key otherwise.
`[].repo`	body	string	—	Repo is the git repository the item is bound to, so a repository's Issues and PRs tabs are filters over this one table.
`[].source`	body	string	—	Source is which surface OPENED it: team, git, crm, helpdesk, cms or agent.
`[].startAt`	body	integer (int64)	—	StartAt is when the work starts, in unix seconds; absent means unscheduled.
`[].status`	body	string	—	Status is the board column: backlog, todo, in_progress, done or canceled, and nothing else.
`[].title`	body	string	—	Title is the item's one-line summary.
`[].updatedAt`	body	integer (int64)	—	UpdatedAt is when it last changed, in unix seconds.
`[].url`	body	string	—	URL is where a person reads the item: its page on the forge or on GitHub.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo task projects issues list <key>

.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.getTaskProjectsByKeyIssues({ key: 'key' });

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

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

resp, _, err := client.TaskAPI.GetTaskProjectsByKeyIssues(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(&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).getTaskProjectsByKeyIssues();

curl https://api.hanzo.ai/v1/task/projects/<key>/issues \
  -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?

PreviousGet issues NextGet projects