Retrieve a Buildkite job's log output via the REST API, choosing between JSON, plain text, or HTML response formats, and know the caveats around size, ranges, and deleting logs.

Documented steps

1. Endpoint: `GET /v2/organizations/{org.slug}/pipelines/{pipeline.slug}/builds/{build.number}/jobs/{job.id}/log` (build-scoped) or the shortcut `GET /v2/organizations/{org.slug}/jobs/{job.id}/log` (org-scoped, no pipeline/build number needed). Requires scope `read_build_logs`. See https://buildkite.com/docs/apis/rest-api/jobs#get-a-jobs-log-output
2. Default response is JSON: `{"url": ..., "content": "<log text>", "size": <bytes>, "header_times": [<nanosecond timestamps>]}`.
3. Request an alternative format via the `Accept` header or file extension: `Accept: text/plain` (or `.../log.txt`) returns raw log content as plain text; `Accept: text/html` (or `.../log.html`) returns the log pre-rendered as HTML via Buildkite's `terminal-to-html` renderer.
4. To check log size without downloading it, send `HEAD` — the response has no body but includes `Content-Length` and `Accept-Ranges: bytes`.
5. To fetch only the tail of a large log, send `GET` with `Accept: text/plain` and `Range: bytes=-N` (suffix range only — explicit start-end or multipart ranges are NOT supported). Success returns `206 Partial Content` with `Content-Range`; `400` for a malformed Range, `416` if the log is empty.
6. To permanently delete a job's stored log, send `DELETE` to the same log URL. Requires scope `write_build_logs`. Success returns `204 No Content`. See https://buildkite.com/docs/apis/rest-api/jobs#delete-a-jobs-log-output