인증
Bearer 토큰으로 API 키를 전송하세요. 키는 반드시 hosting.deploy.manage 권한을 가지고 있어야 하며, 권한이 없는 키는 404가 아닌 403으로 거부됩니다.
이 엔드포인트는 조직 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 environme… |
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 toke… |
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 dif… |
connected_account | string | 예 | The label of the credential connection this repository is read with. |
이 엔드포인트가 반환할 수 있는 오류
401 · 403 · 404 · 422 · 429