hosting

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

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

Autenticazione

Invia una chiave API come token di tipo bearer. La chiave deve disporre dell'autorizzazione hosting.deploy.manage; una chiave sprovvista di tale autorizzazione viene rifiutata con 403 anziché 404.

Questo endpoint non richiede alcun ID organizzazione. La tua chiave identifica già l'organizzazione a cui appartiene e la risposta è limitata ad essa.

Provalo

Sostituisci qualsiasi elemento tra parentesi angolari con i tuoi valori e il segnaposto key con una chiave dalla tua dashboard.

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

Hai effettuato l'accesso? La console API nella tua dashboard inserisce il tuo ID organizzazione reale e la tua chiave personale, ed esegue la richiesta sull'API live in modo da poter vedere la risposta effettiva. Apri questo endpoint nella console API

Dettagli

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

Nome	Tipo	Obbligatorio	Che cos'è
`siteId (path)`	`Uuid`	Sì	Site ID (UUIDv7).

Corpo della richiesta

Nome	Tipo	Obbligatorio	Che cos'è
`provider`	`string`	Sì	—
`owner`	`string`	No	—
`repo`	`string`	Sì	—
`branch`	`string`	No	—
`build_mode`	`BuildMode`	No	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`	No	—
`output_dir`	`string`	No	—
`publish_branch`	`string`	No	—
`auto_deploy`	`boolean`	No	—

Risposta

Nome	Tipo	Obbligatorio	Che cos'è
`site_id`	`Uuid`	Sì	UUIDv7 identifier — sortable by creation time (docs/02 §8).
`provider`	`string`	Sì	The git provider — `github` or `gitlab`. A machine identifier.
`owner`	`string`	Sì	The account or namespace the repository lives under.
`repo`	`string`	Sì	—
`full_name`	`string`	Sì	`owner/repo`, or just the repo when the account owns its namespace.
`branch`	`string`	Sì	The branch a push deploys from.
`build_mode`	`BuildMode`	Sì	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`	Sì	Blank in `publish` mode — a stored command nothing runs would read as a build.
`output_dir`	`string`	Sì	Which directory is published. Blank means the repository root.
`publish_branch`	`string`	Sì	Where CI commits the built output in `ci` mode.
`auto_deploy`	`boolean`	Sì	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`	Sì	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`	Sì	Whether a provider-side hook actually exists. False here with a connection present means pushes are NOT being watched.
`last_delivery_at`	`object`	Sì	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`	Sì	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`	Sì	The label of the credential connection this repository is read with.

Errori che questo endpoint può restituire

401 · 403 · 404 · 422 · 429

PUT /v1/sites/{siteId}/repo