Overview
The Create Heartbeat Check endpoint allows you to create new heartbeat monitoring checks to verify that scheduled processes, cron jobs, and background services are running correctly. Common Use Cases:- Cron Job Monitoring
- Background Process Verification
- Scheduled Task Tracking
- Service Liveness Checks
Authorizations
The Checkly Public API uses API keys to authenticate requests. You can get the API Key here.
Your API key is like a password: keep it secure!
Authentication to the API is performed using the Bearer auth method in the Authorization header and using the account ID.
For example, set Authorization header while using cURL:
curl -H "Authorization: Bearer [apiKey]" "X-Checkly-Account: [accountId]"
Headers
Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general
Query Parameters
Determines whether a new check will automatically be added as a subscriber to all existing alert channels when it gets created.
Body
The name of the check.
"Check"
Determines if the check is running or not.
Determines if any notifications will be send out when a check fails and/or recovers.
[Deprecated] Retry failed check runs. This property is deprecated, and retryStrategy
can be used instead.
Allows to invert the behaviour of when a check is considered to fail. Allows for validating error status like 404.
An array of one or more data center locations where to run this check.
["us-east-1", "eu-central-1"]
Tags for organizing and filtering checks.
["production"]
Alert settings.
When true, the account level alert setting will be used, not the alert setting defined on this check.
The id of the check group this check is part of.
null
The position of this check in a check group. It determines in what order checks are run when a group is triggered from the API or from CI/CD.
x >= 0
null
The runtime version, i.e. fixed set of runtime dependencies, used to execute this check.
2025.04
, 2024.09
, 2024.02
, 2023.09
, 2023.02
, 2022.10
List of alert channel subscriptions.
[]
When true, the check will run in parallel in all selected locations.
How often the check should run in minutes.
x >= 1
Path of the script in the runtime.
Key/value pairs for setting environment variables during check execution. These are only relevant for Browser checks. Use global environment variables whenever possible.
50
An ID reference to a snippet to use in the setup phase of an API check.
An ID reference to a snippet to use in the teardown phase of an API check.
A valid piece of Node.js code to run in the setup phase.
A valid piece of Node.js code to run in the teardown phase.
The response time in milliseconds where a check should be considered degraded.
0 <= x <= 300000
The response time in milliseconds where a check should be considered failing.
0 <= x <= 300000
Response
Created
The name of the check.
"Check"
"d432cf89-010b-4b12-8150-958c8eb1d5ca"
Determines if the check is running or not.
Determines if any notifications will be send out when a check fails and/or recovers.
Tags for organizing and filtering checks.
["production"]
Alert settings.
When true, the account level alert setting will be used, not the alert setting defined on this check.
When true, the check will run in parallel in all selected locations.
HEARTBEAT