hosting

PUT `/v1/sites/{siteId}/repo`

Connect (or re-connect) a repository to a site.

Autentificare

Trimiteți o cheie API ca token de tip bearer. Cheia trebuie să aibă permisiunea hosting.deploy.manage; o cheie care nu o are va fi respinsă cu 403, nu 404.

Acest endpoint nu necesită un ID de organizație. Cheia ta identifică deja organizația căreia îi aparține, iar răspunsul este limitat la aceasta.

Încearcă

Înlocuiți tot ce se află între paranteze unghiulare cu propriile valori și substituentul cheie cu o cheie din tabloul de bord.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/repo \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "provider": <string>, "repo": <string> }'

Autentificat? Consola API din panoul de control îți completează ID-ul real al organizației și propria cheie și rulează cererea în API-ul live, astfel încât să poți vedea răspunsul efectiv. Deschideți acest punct final în consola API

Detalii

Confirms the repository exists on the connected account, stores the connection, and creates or updates the provider-side push webhook — and, when `build_mode` is `ci`, commits the Zinn® build workflow to the repository. The provider work happens before the row is reported as connected, so a hook that could not be created never leaves a row claiming it was. Requires `hosting.deploy.manage`.

Parametri

Nume	Tip	Obligatoriu	Ce este
`siteId (path)`	`Uuid`	Da	Site ID (UUIDv7).

Corp cerere

Nume	Tip	Obligatoriu	Ce este
`provider`	`string`	Da	—
`owner`	`string`	Nu	—
`repo`	`string`	Da	—
`branch`	`string`	Nu	—
`build_mode`	`BuildMode`	Nu	How the published files are produced. `publish` serves the repository's own files — right for plain HTML and for a repo whose generator output is committed. `ci` runs the build…
`build_command`	`string`	Nu	—
`output_dir`	`string`	Nu	—
`publish_branch`	`string`	Nu	—
`auto_deploy`	`boolean`	Nu	—

Răspuns

Nume	Tip	Obligatoriu	Ce este
`site_id`	`Uuid`	Da	UUIDv7 identifier — sortable by creation time (docs/02 §8).
`provider`	`string`	Da	The git provider — `github` or `gitlab`. A machine identifier.
`owner`	`string`	Da	The account or namespace the repository lives under.
`repo`	`string`	Da	—
`full_name`	`string`	Da	`owner/repo`, or just the repo when the account owns its namespace.
`branch`	`string`	Da	The branch a push deploys from.
`build_mode`	`BuildMode`	Da	How the published files are produced. `publish` serves the repository's own files — right for plain HTML and for a repo whose generator output is committed. `ci` runs the build…
`build_command`	`string`	Da	Blank in `publish` mode — a stored command nothing runs would read as a build.
`output_dir`	`string`	Da	Which directory is published. Blank means the repository root.
`publish_branch`	`string`	Da	Where CI commits the built output in `ci` mode.
`auto_deploy`	`boolean`	Da	Whether a push deploys automatically. Off still records every delivery, so a customer can watch pushes arriving before letting us act on them.
`webhook_url`	`string`	Da	The URL the provider was told to deliver to. Computed, never stored — a stored copy would keep naming the origin that was current when the row was written. Blank on an environme…
`webhook_registered`	`boolean`	Da	Whether a provider-side hook actually exists. False here with a connection present means pushes are NOT being watched.
`last_delivery_at`	`object`	Da	When the provider last delivered anything, or null for NEVER. Null is the single most useful diagnostic on this screen: "connected but never delivered" is what a mis-scoped toke…
`last_delivery_note`	`string`	Da	What we did with the last delivery, including when we ignored it. Written for every delivery, because "never delivered" and "delivering, ignored" are different problems with dif…
`connected_account`	`string`	Da	The label of the credential connection this repository is read with.

Erori pe care le poate returna acest punct final

401 · 403 · 404 · 422 · 429

PUT /v1/sites/{siteId}/repo