hosting

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

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

Semua titik akhir hosting

Autentikasi

Kirim kunci API sebagai token bearer. Kunci tersebut harus memiliki izin sites.view; kunci tanpa izin tersebut akan ditolak dengan status 403, bukan 404.

Endpoint ini tidak memerlukan id organisasi. Kunci Anda telah mengidentifikasi organisasi tempatnya berafiliasi, dan respons akan dibatasi untuk organisasi tersebut.

Coba

Ganti apa pun di dalam tanda kurung sudut dengan nilai Anda sendiri, dan placeholder kunci dengan kunci dari dasbor Anda.

curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/deployments/{deploymentId}/build-log \
  -H "Authorization: Bearer zdk_live_…"

Sudah masuk? Konsol API di dasbor Anda akan mengisi ID organisasi asli dan kunci Anda sendiri, serta menjalankan permintaan terhadap API langsung sehingga Anda dapat melihat respons aktualnya. Buka titik akhir ini di konsol API

Detail

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

Parameter

NamaJenisWajibTentang apa ini
siteId (path)UuidYaSite ID (UUIDv7).
deploymentId (path)UuidYaDeployment ID (UUIDv7).
after (query)integerTidakSkip this many lines — the count already rendered.

Tanggapan

NamaJenisWajibTentang apa ini
linesBuildLogLine[]Ya
completebooleanYaWhether 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…
totalintegerYaLines the provider says exist, or `-1` where it publishes no total. Never `0` for unknown, which would read as an empty log.

Kesalahan yang dapat dikembalikan oleh titik akhir ini

401 · 403 · 404 · 422 · 429