service_id in the path. This endpoint returns a paginated list of heartbeats, helping you understand which recurring jobs, scripts, or processes are currently being tracked under that service.Use query parameters such as
limit and page to control pagination and manage large sets of heartbeat monitors efficiently.Use cases:
- Service-level visibility — See all heartbeats linked to a given service for monitoring coverage review.
- Bulk operations — Use the results to prepare for updates or deletions of multiple heartbeat monitors.
- Audit readiness — Verify that all critical background tasks within a service have monitoring in place.
To inspect a specific heartbeat’s details, use the Get Single Heartbeat Monitor endpoint.