Hanzo AI
OpenapiGit

Create webhook

GONE (410). Push-to-deploy belongs to POST https://platform.hanzo.ai/v1/git-webhook, which owns the build system-of-record and dispatches BuildKit Jobs.

POST /v1/git/webhook

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

GONE (410). Push-to-deploy 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.

Every delivery answers 410 whatever it carries — this endpoint reads no body and authenticates nothing.

410 rather than 404, because the address was real and its meaning moved, which is the distinction 410 carries. A 404 from this estate is ambiguous: Hanzo Git serves /v1, so /api/v1 404s too and reads as "the API is switched off". A retired endpoint says it is retired and names its replacement, so the answer carries its own fix.

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 MCP'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