---
title: "Healthz"
method: GET
path: "/healthz"
tags: ["System"]
---

# Healthz

`GET /healthz`

## Request

- Base URL: `https://api.kolens.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.kolens.ai/healthz`
- Auth: none declared

Lightweight liveness endpoint for platform health checks (Railway/Render).

No DB, no Settings, no async dependency — answers the moment the
HTTP server starts accepting connections. This is what Railway's
healthcheckPath in railway.toml points at; if you're tempted to
add anything that could block, stop and add it to /readyz instead.

Also reports the image's git SHA, which is what makes "did the
merge actually go live?" answerable in one unauthenticated request
instead of inferred from a green deploy job.

## Response `200`

Successful Response

- HealthzResponse: Liveness, plus the one fact you cannot get any other way. ``revision`` is the git SHA baked into the image at build time. It exists because "is the merge live?" had no answer from outside: the deploy job reporting success proves a build ran and a health check passed, not that the machine serving traffic is running the commit you merged. #785 shipped and the only way to check was to infer it. The deploy workflow's own comments record a release that looked merged and was live nowhere for 20 minutes. ``None`` when the image was built without the build-arg — local runs, and any older image. Absence means unknown, never "stale".
  - `ok` boolean, required
  - `revision` string, nullable

---

[API](https://skmtc.dev/kolens/apis/kolens-api.md) · [All operations](https://skmtc.dev/kolens/apis/kolens-api/llms.txt) · [OpenAPI document](https://skmtc.dev/kolens/apis/kolens-api/revisions/5d6865ab0a24?raw)