Skip to content

Health checks and update monitoring endpoints for Hoody Code instances. Use these endpoints to monitor service availability, inspect runtime metadata, and detect available updates without affecting heartbeat activity.

Returns standardized service health status with process and runtime info. This endpoint does not count towards heartbeat activity, allowing health checks without keeping Hoody Code artificially alive.

This endpoint takes no parameters.

Terminal window
curl -X GET https://your-host/api/v1/code/health
FieldTypeRequiredDescription
statusstringYesService status (e.g. "ok")
servicestringYesService identifier (e.g. "hoody-code")
builtstring | nullYesISO 8601 build timestamp (mtime of the compiled entry file), or null if unavailable
startedstringYesISO 8601 timestamp when the process started
memoryobject | nullYesProcess memory usage. Contains rss (resident set size in bytes) and heap (V8 heap used in bytes, or null)
fdsinteger | nullYesOpen file descriptor count (from /proc/self/fd), or null if unavailable
pidintegerYesProcess ID
ipstringYesRemote peer IP (req.socket.remoteAddress, never X-Forwarded-For)
userAgentstring | nullYesRequest User-Agent header

Checks for available Hoody Code updates. Queries the GitHub releases API (unless disabled with --disable-update-check). Checks run every 6 hours and the user is notified once per week.

This endpoint takes no parameters.

Terminal window
curl -X GET https://your-host/api/v1/code/update/check
FieldTypeRequiredDescription
currentstringNoCurrent version
lateststringNoLatest available version
updateAvailablebooleanNoWhether a newer version is available