hosting

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

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

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin hosting.deploy.manage; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Endpoint ini tidak memerlukan id organisasi. Kunci Anda telah mengidentifikasi organisasi tempatnya berafiliasi, dan respons akan dibatasi untuk organisasi tersebut.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

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

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

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`.

Parameter

Nama	Jenis	Wajib	Tentang apa ini
`siteId (path)`	`Uuid`	Ya	Site ID (UUIDv7).

Isi permintaan

Nama	Jenis	Wajib	Tentang apa ini
`provider`	`string`	Ya	—
`owner`	`string`	Tidak	—
`repo`	`string`	Ya	—
`branch`	`string`	Tidak	—
`build_mode`	`BuildMode`	Tidak	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`	Tidak	—
`output_dir`	`string`	Tidak	—
`publish_branch`	`string`	Tidak	—
`auto_deploy`	`boolean`	Tidak	—

Tanggapan

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

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429

PUT /v1/sites/{siteId}/repo