Task
Hanzo Task: boards, the work items on them, and the filters that make a board.
Also for this capability: API · CLI · SDKs
Hanzo Task: boards, the work items on them, and the filters that make a board.
| Base URL | https://api.hanzo.ai |
| Operations | 13 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Specification
Specification pending — no HIP in hanzoai/hips declares capability: task yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.
Four surfaces
| Surface | Reaches this capability as | Coverage |
|---|---|---|
| REST | task at its own prefix | 13 operations |
| CLI | hanzo task … | 13 of 13 |
| SDK | — | no published client declares one yet — regenerating the clients is what adds them |
| MCP | tool tasks on https://api.hanzo.ai/v1/mcp | 20 operations, 0 under the document's own id — ask describe for the rest |
Quickstart
export HANZO_API_KEY=sk-... # console.hanzo.ai → API keysThen the first call — a read that needs nothing but the key. GET /v1/task/board, operation get_task_board:
hanzo task boardimport { Configuration, TaskApi } from 'hanzoai';
const api = new TaskApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTaskBoard();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_board()cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.TaskAPI.GetTaskBoard(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_board(&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).getTaskBoard();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/task/board \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches task through the tasks tool, which names its 20 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_tasks"
}
}
}'Answers 200 with task.issueView[] — ok.
Endpoints
| Endpoint | What it does |
|---|---|
GET /v1/task/board | Returns a board's issues — work items with their column, priority, assignee, labels and schedule. |
GET /v1/task/issues | Answers across every project in the org. |
POST /v1/task/projects/{key}/issues/{num}/claim | Takes an issue: it becomes yours and it moves to in_progress. |
GET /v1/task/projects/{key}/issues/{num} | Returns ONE work item in full — its description included. |
PATCH /v1/task/projects/{key}/issues/{num} | Edits a work item — rename it, rewrite it, move it to another column, or re-prioritise it. |
GET /v1/task/projects/{key}/issues | Returns a board's issues — work items with their column, priority, assignee, labels and schedule. |
POST /v1/task/projects/{key}/issues | Opens a work item on the board — an issue on that repository on the deployment's forge, filed as YOU. |
GET /v1/task/projects/{key} | Returns one board of your org by its key — the repository name. |
PATCH /v1/task/projects/{key} | Refused — a board is a repository on the forge |
DELETE /v1/task/projects/{key} | Refused — a board is a repository on the forge |
GET /v1/task/projects | Returns the boards of your org — the places your work actually is. |
POST /v1/task/projects | Refused — a board is a repository on the forge |
GET /v1/task/rooms/{room} | Summarises one room's work. |
How is this guide?