Skip to content
Hoody.com

Hoody Cron service provides scheduled task management for your container. This page covers the service’s operational endpoints, including a health probe for monitoring and endpoints that expose the service’s OpenAPI specification for client generation and introspection.

All endpoints are served from your container’s Cron instance at https://{projectId}-{containerId}-cron-1.{server}.containers.hoody.icu.

Returns a snapshot of the Cron service’s runtime status, including process information, resource usage, and startup metadata. Use this endpoint for liveness and readiness probes.

This endpoint takes no parameters.

Terminal window
curl https://myproject-mycontainer-cron-1.us-east.containers.hoody.icu/health
FieldTypeRequiredDescription
builtstring | nullNoBuild timestamp or identifier for the running service
fdsinteger | nullNoNumber of open file descriptors held by the process
ipstringYesIP address the service is bound to
memoryobject | nullNoMemory usage snapshot containing heap (bytes) and rss (bytes)
pidintegerYesOperating system process ID
servicestringYesService identifier (cron)
startedstringYesISO 8601 timestamp of when the service started
statusstringYesHealth status indicator (typically "ok")
user_agentstring | nullNoUser agent string of the most recent client, if available

The service publishes its own API contract in both JSON and YAML formats. These endpoints are useful for generating typed clients, validating integrations, or exploring the available operations at runtime.

Returns the Cron service’s OpenAPI specification as a JSON document.

This endpoint takes no parameters.

Terminal window
curl https://myproject-mycontainer-cron-1.us-east.containers.hoody.icu/openapi.json

Returns the Cron service’s OpenAPI specification as a YAML document.

This endpoint takes no parameters.

Terminal window
curl https://myproject-mycontainer-cron-1.us-east.containers.hoody.icu/openapi.yaml