hosting

POST `/v1/webhooks/git/{provider}/{repoId}`

Ingest a push from a customer's git provider and deploy it.

Authentication

This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.

This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X POST https://api.zinndigital.com/v1/webhooks/git/{provider}/{repoId}

Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console

Details

Unauthenticated by design — the git provider holds no Zinn® credential, so the signature over the raw body is the authentication. A verified push on the branch a repository is wired to triggers a deploy of that site. ⛔ The repoId in the path identifies which connection's secret verifies the signature; it is not a permission. A request whose signature does not verify is refused before anything is read from it.

Parameters

Name	Type	Required	What it is
`provider (path)`	`string<github, gitlab, bitbucket>`	Yes	The git host that sent the push.
`repoId (path)`	`string`	Yes	The connected repository this push belongs to.

Response

Name	Type	Required	What it is
`status`	`string<handled, ignored, duplicate>`	Yes	`handled` — acted on. `ignored` — a valid event of a type Zinn® does not consume. `duplicate` — already processed; Stripe may stop redelivering.

Errors this endpoint can return

400 · 404

POST /v1/webhooks/git/{provider}/{repoId}