Hoody Cron
Section titled “Hoody Cron”Hoody Cron manages a container’s scheduled jobs. It exposes two APIs and a health probe. Use the Managed Entries API to create, list, get, update, and delete scheduled jobs with first-class fields for the schedule, command, name, comment, enabled, and expires_at. Use the Crontab API to read and write a user’s raw crontab for cases that need full crontab semantics. The health endpoint documented on this page reports the runtime status of the cron worker, independent of either API.
Health
Section titled “Health”GET /api/v1/cron/health
Section titled “GET /api/v1/cron/health”Returns the current health and runtime metadata for the cron worker.
This endpoint takes no parameters.
Response
Section titled “Response”200: returned when the worker is healthy and accepting requests.
| Name | Type | Required | Description |
|---|---|---|---|
status | string | Yes | Health status reported by the worker |
service | string | Yes | Service identifier (always hoody-cron) |
started | string | Yes | ISO 8601 timestamp at which the worker started |
pid | integer | Yes | Process ID of the worker |
ip | string | Yes | IP address of the connecting peer |
built | string | null | No | Build identifier of the worker, or null when not recorded |
fds | integer | null | No | Number of open file descriptors, or null when not recorded |
memory | object | null | No | Memory usage of the worker, or null when not recorded |
user_agent | string | null | No | User-Agent header supplied by the caller, or null when absent or invalid |
When memory is present it carries:
| Name | Type | Required | Description |
|---|---|---|---|
rss | integer | Yes | Resident set size, in bytes |
heap | integer | null | No | Heap usage in bytes, or null when not recorded |
curl https://67e89abc123def456789abcd-890abcdef12345678901cdef-cron-1.node-example-1.containers.hoody.com/api/v1/cron/healthimport { HoodyClient } from 'hoody-sdk';
const client = new HoodyClient({ baseURL: 'https://67e89abc123def456789abcd-890abcdef12345678901cdef-cron-1.node-example-1.containers.hoody.com', token: process.env.HOODY_TOKEN });
await client.cron.kit.getHealth();{ "status": "ok", "service": "hoody-cron", "started": "2026-01-15T08:30:00.000Z", "pid": 42, "ip": "10.0.0.5", "built": "2026-01-14T22:10:00.000Z", "fds": 12, "memory": { "rss": 33554432, "heap": null }, "user_agent": "hoody-cron/1.4.2"}