hosting
GET /v1/sites/{siteId}/deployments/{deploymentId}
One deploy, with its build log.
Authentication
Send an API key as a bearer token. The key must carry the sites.view permission; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/deployments/{deploymentId} \
-H "Authorization: Bearer zdk_live_…"Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
The log is written line by line as the build runs rather than at the end, so it is readable while a deploy is in flight and present on one that hangs. Requires sites.view.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
deploymentId (path) | Uuid | Yes | Deployment ID (UUIDv7). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
id | Uuid | Yes | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
site_id | Uuid | Yes | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
target | DeployTarget | Yes | Where the site is published from. fleet is our own managed fleet; the rest are managed edge hosts, deployed to from a pooled account of ours or the customer's own connected one.… |
status | DeployStatus | Yes | idle means the site has never been deployed. It is reported, never stored — a stored idle would be a second way to say "no deployments" that could contradict the first. |
trigger | DeployTrigger | Yes | What caused the deploy. Stored because requested_by cannot answer it for a push — the actor there is a webhook delivery, not a person. |
repo | object | Yes | — |
branch | object | Yes | — |
commit | object | Yes | — |
commit_message | object | Yes | — |
live_url | object | Yes | — |
message | object | Yes | Why it failed, else null. Rendered to the customer verbatim. |
requested_by | string | Yes | — |
created_at | string | Yes | — |
started_at | object | Yes | — |
finished_at | object | Yes | — |
log | string | Yes | The build log, one timestamped line per step. Truncated from the FRONT when long — the end of a build log is where the failure is. |
Errors this endpoint can return
401 · 403 · 404 · 429