Health endpoints
Public health endpoints
Hamstik exposes two unauthenticated, machine-readable health endpoints. They are intended for deployment checks and load balancer probes; they do not expose database details, configuration, exception messages, or migration information.
Liveness
GET https://hamstik.com/api/health200 OK with status: "ok" means the Hamstik process can serve HTTP. This
probe is deliberately lightweight and does not depend on PostgreSQL or other
downstream services. The response also includes the application version and a
server timestamp for compatibility with existing deployment checks.
Readiness
GET https://hamstik.com/api/ready200 OK with status: "ready" means the instance passed its bounded database
readiness probe. A failed probe returns 503 Service Unavailable with only
status: "unready".
Both endpoints return Cache-Control: no-store and an X-Request-Id. Health
responses never include credentials, connection strings, internal exception
details, or other diagnostic payloads.