hosting

GET /v1/sites/{siteId}/deployments/{deploymentId}/build-log

The hosting provider's own build log for one deploy.

All hosting endpoints

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}/build-log \
  -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

Distinct from the `log` on `GET /deployments/{deploymentId}`, which is the platform's own five steps and is the same five whether a build succeeded or failed. When a build fails this is the only text that says WHY. Tail it with `after` while `complete` is false; `after` is a line offset so a live tail is incremental rather than re-fetching a growing log. A provider that publishes no build log, or a deploy that rebuilt nothing, returns `UNPROCESSABLE_ENTITY` with the reason — never an empty log, which would read as "your build printed nothing". Requires `sites.view`.

Parameters

NameTypeRequiredWhat it is
siteId (path)UuidYesSite ID (UUIDv7).
deploymentId (path)UuidYesDeployment ID (UUIDv7).
after (query)integerNoSkip this many lines — the count already rendered.

Response

NameTypeRequiredWhat it is
linesBuildLogLine[]Yes
completebooleanYesWhether the build has finished producing lines. Read from the deployment's terminal state, never from "no new lines this time" — a stalled build and a finished one produce the s…
totalintegerYesLines the provider says exist, or `-1` where it publishes no total. Never `0` for unknown, which would read as an empty log.

Errors this endpoint can return

401 · 403 · 404 · 422 · 429