Hanzo
OpenapiTodo

Refused — a board is a repository on the forge — POST /v1/todo/projects

Answers 405. A todo board IS a repository on this deployment's forge, so creating, renaming and deleting one is a FORGE operation carried out with FORGE…

POST /v1/todo/projects

Addresshttps://api.hanzo.ai/v1/todo/projects
MethodPOST
Operationpost_todo_projects
AuthAuthorization: Bearer $HANZO_API_KEY

Answers 405. A todo board IS a repository on this deployment's forge, so creating, renaming and deleting one is a FORGE operation carried out with FORGE permissions.

Offering it here would put a second door on the same object, guarded by this surface instead of by the forge — a weaker guard on the same thing. So the route exists and refuses, rather than 404ing: "not this service's job" and "no such thing" are different facts, and the body names the forge so a caller knows where the job IS done.

What this surface DOES own is the work on a board: list the boards you can see, read and file their issues, move a card between columns, and read the schedule a milestone is. Those are the routes beside this one.

Request

The document declares no body for POST /v1/todo/projects. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_todo_projects, which answers from the running route.

Response

The document declares no response body for this operation. It answers 200 on success and the platform error shape on failure — see Errors.

Examples

hanzo todo projects create

Todo API · All Hanzo APIs · Interactive reference

How is this guide?

On this page