hosting

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

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

Аутентификација

Пошаљите API кључ као bearer токен. Кључ мора имати дозволу hosting.deploy.manage; кључ без ње се одбија уз 403, а не 404.

Ова крајња тачка не прихвата id организације. Ваш кључ већ идентификује организацију којој припада, а одговор је ограничен на њу.

Испробајте

Замените све што је у угластим заградама сопственим вредностима, а чувар места кључа кључем са своје контролне табле.

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

Пријављени сте? API конзола на вашој контролној табли попуњава ваш прави id организације и ваш сопствени кључ, и покреће захтев према живом API-ју како бисте могли да видите стварни одговор. Отворите ову крајњу тачку у API конзоли

Детаљи

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.

Параметри

Назив	Тип	Обавезно	Шта је ово
`siteId (path)`	`Uuid`	Да	Site ID (UUIDv7).

Тело захтева

Назив	Тип	Обавезно	Шта је ово
`provider`	`string`	Да	—
`owner`	`string`	Не	—
`repo`	`string`	Да	—
`branch`	`string`	Не	—
`build_mode`	`BuildMode`	Не	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`	Не	—
`output_dir`	`string`	Не	—
`publish_branch`	`string`	Не	—
`auto_deploy`	`boolean`	Не	—

Одговор

Назив	Тип	Обавезно	Шта је ово
`site_id`	`Uuid`	Да	UUIDv7 identifier — sortable by creation time (docs/02 §8).
`provider`	`string`	Да	The git provider — `github` or `gitlab`. A machine identifier.
`owner`	`string`	Да	The account or namespace the repository lives under.
`repo`	`string`	Да	—
`full_name`	`string`	Да	`owner/repo`, or just the repo when the account owns its namespace.
`branch`	`string`	Да	The branch a push deploys from.
`build_mode`	`BuildMode`	Да	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`	Да	Blank in `publish` mode — a stored command nothing runs would read as a build.
`output_dir`	`string`	Да	Which directory is published. Blank means the repository root.
`publish_branch`	`string`	Да	Where CI commits the built output in `ci` mode.
`auto_deploy`	`boolean`	Да	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`	Да	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 environment…
`webhook_registered`	`boolean`	Да	Whether a provider-side hook actually exists. False here with a connection present means pushes are NOT being watched.
`last_delivery_at`	`object`	Да	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 token…
`last_delivery_note`	`string`	Да	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…
`connected_account`	`string`	Да	The label of the credential connection this repository is read with.

Грешке које ова крајња тачка може вратити

401 · 403 · 404 · 422 · 429

PUT /v1/sites/{siteId}/repo