hosting

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

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

Doğrulama

API açarını bearer token kimi göndərin. Açar hosting.deploy.manage icazəsinə malik olmalıdır; bu icazəsi olmayan açar 404 deyil, 403 xətası ilə rədd edilir.

Bu endpoint heç bir təşkilat ID-si tələb etmir. Sizin açarınız artıq aid olduğu təşkilatı müəyyən edir və cavab həmin təşkilat üçün məhdudlaşdırılır.

Sınaqdan keçir

Bucaqlı mötərizələrdə olan hór şeyi öz qiymətlərinizlə, açar yertutucusunu isə idarə panelinizdən bir açarla əvəz edin.

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

Sistemə daxil olmusunuz? İdarə panelinizdəki API konsolu real təşkilatınızın identifikatorunu və öz açarınızı avtomatik doldurur, sorğunu canlı API-yə qarşı icra edir ki, siz faktiki cavabı görə biləsiniz. Bu son nöqtəni API konsolunda açın

Təfərrüatlar

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

Parametrlər

Ad	Tip	Tələb olunur	Nədir
`siteId (path)`	`Uuid`	Bəli	Site ID (UUIDv7).

Sorğu gövdəsi

Ad	Tip	Tələb olunur	Nədir
`provider`	`string`	Bəli	—
`owner`	`string`	Xeyr	—
`repo`	`string`	Bəli	—
`branch`	`string`	Xeyr	—
`build_mode`	`BuildMode`	Xeyr	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`	Xeyr	—
`output_dir`	`string`	Xeyr	—
`publish_branch`	`string`	Xeyr	—
`auto_deploy`	`boolean`	Xeyr	—

Cavab

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

Bu son nöqtənin qaytara biləcəyi xətalar

401 · 403 · 404 · 422 · 429

PUT /v1/sites/{siteId}/repo