# List issues — GET /v1/task/issues

URL: https://docs.hanzo.ai/docs/openapi/task/get-task-issues

> Answers across every project in the org.

`GET /v1/task/issues`

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

|               |                                        |
| ------------- | -------------------------------------- |
| **Address**   | `https://api.hanzo.ai/v1/task/issues`  |
| **Method**    | `GET`                                  |
| **Operation** | `get_task_issues`                      |
| **Auth**      | `Authorization: Bearer $HANZO_API_KEY` |

Answers across every project in the org.

The org comes from the validated principal and never from the request: a
caller able to name the org could read another tenant's backlog, and a search
is exactly the shape that would quietly return it.

## Request

9 fields.

| Field      | In    | Type    | Required | Description                                                                                                                                                                                        |
| ---------- | ----- | ------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `q`        | query | string  | —        | Q matches an issue's title or description.                                                                                                                                                         |
| `project`  | query | string  | —        | Project narrows to one team key; "" searches every project in the org, which is the point of this op.                                                                                              |
| `status`   | query | string  | —        | Status keeps one board column: backlog, todo, in\_progress, done, canceled.                                                                                                                        |
| `kind`     | query | string  | —        | Kind keeps one shape: issue, pr, epic.                                                                                                                                                             |
| `repo`     | query | string  | —        | Repo keeps issues bound to one git repository.                                                                                                                                                     |
| `room`     | query | string  | —        | Room keeps issues bound to one collaboration room, spelled "\<space>\_\<room>" — the exact value GET /v1/meet/call answers with, so a channel's call and its task list name the room the same way. |
| `source`   | query | string  | —        | Source keeps one origin: team, git, crm, helpdesk, cms, agent.                                                                                                                                     |
| `assignee` | query | string  | —        | Assignee keeps issues held by one person.                                                                                                                                                          |
| `limit`    | query | integer | —        | Limit caps the answer; 0 means the default, and anything above the ceiling is clamped rather than refused — a search that errors on being too broad teaches people to guess.                       |

## Response

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

`200` body — 13 fields.

| Field               | In   | Type             | Always | Description                                                                                                                                |
| ------------------- | ---- | ---------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `count`             | body | integer (int64)  | —      | Count is how many rows Issues carries — the size of THIS answer after the cap, not how many issues matched.                                |
| `issues`            | body | task.issueHit\[] | —      | Issues are the matching rows grouped by status and oldest-first within a group, capped by the search's limit (50 by default, 200 at most). |
| `issues[].assignee` | body | string           | —      | Assignee is who holds the work.                                                                                                            |
| `issues[].kind`     | body | string           | —      | Kind is what the row IS: issue, pr or epic.                                                                                                |
| `issues[].number`   | body | integer (int64)  | —      | Number is the issue's number on that board, from 1 and monotonic there.                                                                    |
| `issues[].priority` | body | string           | —      | Priority is urgent, high, medium, low or none.                                                                                             |
| `issues[].project`  | body | string           | —      | Project is the board key the issue is on.                                                                                                  |
| `issues[].repo`     | body | string           | —      | Repo is the git repository the issue is bound to, empty when it is not repo-bound.                                                         |
| `issues[].room`     | body | string           | —      | Room is the collaboration room the issue belongs to, spelled "\<space>\_\<room>" — empty when it is not room-bound, which is most of them. |
| `issues[].source`   | body | string           | —      | Source is which surface opened it: team, git, crm, helpdesk, cms or agent.                                                                 |
| `issues[].status`   | body | string           | —      | Status is the board column: backlog, todo, in\_progress, done or canceled.                                                                 |
| `issues[].title`    | body | string           | —      | Title is the issue's one-line summary — what the q filter matched, along with the description.                                             |
| `issues[].url`      | body | string           | —      | URL is the row's external anchor — its extRef — which is a link only when the feeder sent one.                                             |

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

## Examples

**CLI**

```bash
hanzo task issues
```

**SDK**

**.ts**

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

const api = new TaskApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTaskIssues();
```

**.py**

```python
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_issues()
```

**.go**

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

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

**.rs**

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

**.java**

```java
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).getTaskIssues();
```

**HTTP**

```bash
curl https://api.hanzo.ai/v1/task/issues \
  -H "Authorization: Bearer $HANZO_API_KEY"
```

**MCP**

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:

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

---

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