OrdinateDB

Documentation

product Pre-releaseunwritten sections are marked
GET/v1/healthz

Report process liveness

operation ID: get_v1_healthz

Overview

Report process liveness. The service-health operation reports whether the HTTP process is alive without requiring authentication or model access.

When to use it

  • Use it when an application needs to report process liveness.
  • Use it when a load balancer, container orchestrator, or deployment check needs a lightweight liveness signal.

Quick example

Set the base URL and replace generated identifiers or credentials with values from your installation.

cURL

curl --request GET \
  --url "$ORDINATE_URL/v1/healthz"

Expected output · 200

The literal text `ok`

The response uses the documented non-JSON media type.

The cURL request supplies the documented path and query values and asks OrdinateDB to report process liveness. The documented 200 response is the literal text `ok`.

How it works

Liveness confirms that the process can answer HTTP; it does not replace the separate model-readiness check.

Reference

Required capability
anonymous
Authorization scope
none

Parameters

No parameters.

Request body

This operation has no request body.

Responses

200The literal text `ok`

text/plain

string

Code examples

These examples are generated from the source contract. Replace the base URL, credentials, identifiers, and minimal generated values for your instance.

JavaScript

const ordinateUrl = "http://localhost:8080";
const token = "<bearer-token>";

const response = await fetch(`${ordinateUrl}/v1/healthz`, {
  method: "GET"
});

if (!response.ok) {
  throw new Error(`OrdinateDB returned ${response.status}: ${await response.text()}`);
}

const data = await response.text();
console.log(data);