Update check
healthchecksio_update_checkDestructive
UPDATES an existing check by UUID — this MODIFIES live monitoring config. Send only the fields you want to change (timeout and schedule remain mutually exclusive). Healthchecks: POST /checks/{uuid}. Returns the updated check.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | Server's timezone for the cron `schedule`, e.g. "Europe/Riga". | |
| desc | No | Free-form description of the check. | |
| name | No | Human-readable name for the check. | |
| slug | No | URL slug (used for slug-based ping URLs). | |
| tags | No | Space-separated list of tags, e.g. "prod db backups". | |
| uuid | Yes | The check's UUID to update. | |
| grace | No | Grace time in seconds after the deadline before the check goes down. | |
| unique | No | Dedupe fields — if a check already matches on these (e.g. ["name"]), it is returned instead of created. | |
| methods | No | Allowed ping HTTP methods: "" (any) or "POST" (POST-only). | |
| timeout | No | Expected period between pings, in seconds (60..31536000). Mutually exclusive with `schedule`. | |
| channels | No | Integrations to assign: "*" for all, or a comma-separated list of integration ids. | |
| schedule | No | Cron expression for the expected ping schedule (e.g. "15 5 * * *"). Mutually exclusive with `timeout`; requires `tz`. | |
| manual_resume | No | If true, a paused check does not auto-resume on the next ping (resume manually). |