hosting

PUT /v1/sites/{siteId}/repo

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

Tous les points de terminaison hosting

Authentification

Envoyez une clé API en tant que jeton du porteur. La clé doit posséder l'autorisation hosting.deploy.manage ; une clé qui ne l'a pas est refusée avec le code 403, et non 404.

Cet endpoint ne prend aucun identifiant d'organisation. Votre clé identifie déjà l'organisation à laquelle elle appartient, et la réponse y est limitée.

Essayer

Remplacez tout ce qui se trouve entre crochets par vos propres valeurs, et le espace réservé à la clé par une clé de votre tableau de bord.

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

Connecté ? La console d'API de votre tableau de bord saisit votre véritable ID d'organisation ainsi que votre propre clé, et exécute la requête sur l'API de production afin que vous puissiez voir la réponse réelle. Ouvrir ce point de terminaison dans la console API

Détails

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

Paramètres

NomTypeObligatoireQu'est-ce que c'est
siteId (path)UuidOuiSite ID (UUIDv7).

Corps de la requête

NomTypeObligatoireQu'est-ce que c'est
providerstringOui
ownerstringNon
repostringOui
branchstringNon
build_modeBuildModeNonHow 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_commandstringNon
output_dirstringNon
publish_branchstringNon
auto_deploybooleanNon

Réponse

NomTypeObligatoireQu'est-ce que c'est
site_idUuidOuiUUIDv7 identifier — sortable by creation time (docs/02 §8).
providerstringOuiThe git provider — `github` or `gitlab`. A machine identifier.
ownerstringOuiThe account or namespace the repository lives under.
repostringOui
full_namestringOui`owner/repo`, or just the repo when the account owns its namespace.
branchstringOuiThe branch a push deploys from.
build_modeBuildModeOuiHow 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_commandstringOuiBlank in `publish` mode — a stored command nothing runs would read as a build.
output_dirstringOuiWhich directory is published. Blank means the repository root.
publish_branchstringOuiWhere CI commits the built output in `ci` mode.
auto_deploybooleanOuiWhether a push deploys automatically. Off still records every delivery, so a customer can watch pushes arriving before letting us act on them.
webhook_urlstringOuiThe 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_registeredbooleanOuiWhether a provider-side hook actually exists. False here with a connection present means pushes are NOT being watched.
last_delivery_atobjectOuiWhen 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_notestringOuiWhat 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_accountstringOuiThe label of the credential connection this repository is read with.

Erreurs que cet point de terminaison peut renvoyer

401 · 403 · 404 · 422 · 429