Hanzo
OpenapiTasks

Redirect to the tasks API root — POST /v1/tasks

Answers 307 with Location /v1/tasks/ — this address serves nothing itself.

POST /v1/tasks

Addresshttps://api.hanzo.ai/v1/tasks
MethodPOST
Operationpost_tasks
AuthAuthorization: Bearer $HANZO_API_KEY

Answers 307 with Location /v1/tasks/ — this address serves nothing itself. The redirect is a routing fact derived from the engine's subtree, decided before any handler runs, so it is the same on every method.

A 307 preserves both the method and the body, so a client that follows redirects re-sends the request unchanged to /v1/tasks/ and nothing is lost. A client that does NOT follow redirects sees only the 307 and performs no work — address /v1/tasks/ directly and the hop disappears.

Request

The document declares no body for POST /v1/tasks. 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_tasks, 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 tasks create

Tasks API · All Hanzo APIs · Interactive reference

How is this guide?

On this page