List build logs
OpenAPI contract
- Method
- GET
- Path
/api/v1/builds/{taskId}/logs- Security
- jwtBearer (bearer) OR automationKey (bearer)
- Response status
- 200 400 401 403 404 429 500
Request and response schemas
JSON
{
"requestBody": {},
"responses": {
"200": {
"description": "Build logs",
"content": {
"application/json": {
"$ref": "#/components/schemas/CompileLogPage"
}
}
},
"400": {
"description": "Invalid request",
"content": {
"application/json": {
"$ref": "#/components/schemas/RequestError"
}
}
},
"401": {
"description": "Authentication required or invalid",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"403": {
"description": "Authenticated but not permitted",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"404": {
"description": "Requested build was not found",
"content": {
"application/json": {
"$ref": "#/components/schemas/ApiError"
}
}
},
"429": {
"description": "HTTP rate limit or API-key NCU usage limit exceeded",
"content": {
"application/json": {
"$ref": "#/components/schemas/RateLimitError"
}
}
},
"500": {
"description": "Unexpected server error",
"content": {
"application/json": {
"$ref": "#/components/schemas/ApiError"
}
}
}
}
}Read a bounded slice of a build log with a JWT or an nfy_ key carrying build:read. A project task additionally requires effective build:read capability on its project; a legacy or ad-hoc task uses its exact-owner fallback. from is a zero-based line offset and limit is capped at 5,000 lines. Negative values are clamped to zero; offsets beyond the current tail produce an empty slice.
Use the returned to offset as the next from value and totalLines to understand the current tail. A build may not have created its log yet, in which case the result is empty. Log storage follows task cleanup, so retained task metadata does not guarantee that historical logs remain available.