Update Heartbeat Monitor

Update the configuration of an existing heartbeat monitor by providing its heartbeat_id in the path and submitting the updated values in the request body. You can modify fields such as the name or the interval that determines when a missed heartbeat should be treated as a failure.

This operation helps ensure that heartbeat monitors stay aligned with the expected behavior of the processes or systems they track.

Use cases:

• Rename jobs — Update the name of the heartbeat resource to reflect a new job title or function.
• Change incident trigger interval — Update the interval that defines how long the system waits before flagging a missed heartbeat as an incident.
• Reorganize services — Move a heartbeat to a different service context if team responsibilities or architecture shift.

To review a heartbeat's current configuration before updating, use the Get Single Heartbeat Monitor endpoint.

Authorization: Bearer YOUR_TOKEN

Expected Behavior:

• On success, the heartbeat resource will be updated, and a confirmation message will be returned.
• If the request is invalid or cannot be processed, an error message will indicate the issue, such as an invalid URL; if the heartbeat resource is not found, an error will specify that the heartbeat does not exist.