Change, pause or resume a heartbeat check
heartbeat_updateChange a heartbeat check or pause it (never alerts) or resume it (a fresh deadline from now); pausing or resuming again changes nothing, but a repeat call is not a no-op: the same period or grace again moves a waiting check's deadline. A new period or grace counts from the last ping (from now while waiting; due at once if that already ran out). Only a real ping recovers a down check: changing it keeps it down with its open incident and sends no up message (pausing closes the incident, also without one), and the new period and grace count from the ping that ends it. An unknown heartbeat_id answers heartbeat_not_found; heartbeat_remove stops watching for good.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"instance_id": "hbt_exampleexampleexample2",
"heartbeat_id": "hbc_exampleexampleexample2",
"period_minutes": 60
},
"name": "heartbeat_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | New label. | |
| status | No | paused: never alerts; active: a fresh deadline from now. | |
| email_owner | No | Owner emails on or off. | |
| instance_id | Yes | Utility instance id from buy or list_utilities. | |
| heartbeat_id | Yes | heartbeat id (hbc_...) from heartbeat_add or heartbeat_status. | |
| grace_minutes | No | New grace in minutes. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. | |
| period_minutes | No | New period in minutes. | |
| inbox_instance_id | No | Another inbox, or null for none. |