Skip to content

The Hoody SQLite service combines a managed SQL execution layer with a high-performance key-value store. The endpoints in this section let you run SQL transactions, perform atomic and batch key-value operations, inspect stored keys with time-travel queries, and scrape health metrics for observability dashboards and liveness probes.

SQL Operations

Execute SQL transactions, create databases, and run queries against Hoody-managed databases.

View SQL Operations →

Key-Value Store

Overview of the distributed KV Store, key listing, and metadata endpoints.

View KV Store →

Liveness and observability endpoints for the SQLite service. These endpoints expose service identity, process-level counters, and cache pressure snapshots for monitoring, alerting, and load-balancer probes.

Liveness/observability endpoint. Returns service identity (status/service/built/started), process-level memory and file-descriptor counters (pid/memory/fds), and hardening snapshots (cache/counters). One scrape covers both liveness and observability signals.

This endpoint takes no parameters.

Terminal window
curl https://api.hoody.io/api/v1/sqlite/health

SDK usage

const health = await client.sqlite.health.getHealth();

Returns only the cache sub-object from /health. Dedicated endpoint for dashboards that poll cache pressure without re-reading process-level memory and file-descriptor counters.

This endpoint takes no parameters.

Terminal window
curl https://api.hoody.io/api/v1/sqlite/health/cache

SDK usage

const cache = await client.sqlite.health.getHealthCache();