Hanzo
OpenapiGit

Retired — forge pushes build via platform.hanzo.ai

GONE (410). This was the canonical forge's push-to-deploy door, and it never dispatched a build in its life.

POST /v1/git/webhook

Addresshttps://api.hanzo.ai/v1/git/webhook
MethodPOST
Operationpost_git_webhook
AuthAuthorization: Bearer $HANZO_API_KEY

GONE (410). This was the canonical forge's push-to-deploy door, and it never dispatched a build in its life.

It handed each verified push to cloud.OnGitPush, a single-registrant seam whose only registrant lives in apps/platform. cloud runs each app as its own OS process, so in the git process that builder is nil forever — and this handler answered 204 either way. Delivered, signature valid, green on the forge's hook page, and nothing built.

Push-to-deploy now belongs to POST https://platform.hanzo.ai/v1/git-webhook, which owns the build system-of-record and dispatches BuildKit Jobs. git.hanzo.ai delivers there through ONE forge-wide system webhook covering every repository; a repo opts in by committing hanzo.yml, not by owning a hook of its own.

The route is kept, and answers 410 naming that address, precisely so a misdirected delivery says what is wrong. Deleting it would 404, and a 404 here reads as 'the API is switched off' — the wrong conclusion this estate has already drawn twice.

Request

The document declares no body for POST /v1/git/webhook. 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_git_webhook, 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 git webhook

Git API · All Hanzo APIs · Interactive reference

How is this guide?

On this page