hosting
GET /v1/sites/{siteId}/deployments/{deploymentId}/build-log
The hosting provider's own build log for one deploy.
身份验证
请将 API 密钥作为 bearer 令牌发送。该密钥必须具有 sites.view 权限；缺少该权限的密钥将被拒绝并返回 403 状态码，而非 404。
此端点不需要组织 ID。您的密钥已用于识别其所属的组织，且响应范围也仅限于该组织。
免费试用
将尖括号中的内容替换为您自己的值，并将键占位符替换为您仪表板中的一个键。
curl -X GET https://api.zinndigital.com/v1/sites/{siteId}/deployments/{deploymentId}/build-log \
-H "Authorization: Bearer zdk_live_…"已登录？您仪表板中的 API 控制台会自动填入您真实的组织 ID 和您自己的密钥，并针对实时 API 运行请求，以便您查看实际的响应。 在 API 控制台中打开此端点
详细信息
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`.
参数
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
siteId (path) | Uuid | 是 | Site ID (UUIDv7). |
deploymentId (path) | Uuid | 是 | Deployment ID (UUIDv7). |
after (query) | integer | 否 | Skip this many lines — the count already rendered. |
响应
| 名称 | 类型 | 必填 | 内容简介 |
|---|---|---|---|
lines | BuildLogLine[] | 是 | — |
complete | boolean | 是 | Whether 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… |
total | integer | 是 | Lines the provider says exist, or `-1` where it publishes no total. Never `0` for unknown, which would read as an empty log. |
此端点可能返回的错误
401 · 403 · 404 · 422 · 429