Update a heartbeat check
Updates a Heartbeat check.
Path parameters
Query parameters
Determines whether a new check will automatically be added as a subscriber to all existing alert channels when it gets created.
Determines whether a new check will automatically be added as a subscriber to all existing alert channels when it gets created.
Headers
Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general
Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general
Request body
Example request
{
"name": "Check",
"locations": [
"us-east-1",
"eu-central-1"
],
"tags": [
"production"
],
"alertChannelSubscriptions": [],
"environmentVariables": [
{
"key": "API_KEY"
}
]
}Response
Successful
Example response
{
"alertChannels": {
"sms": [
{
"number": "+549110000000",
"name": "SMS Alert"
}
]
}
}Changes
Changed in 2 of the 4 revisions of this API.14446
- ▲
request body became required
request-body-became-required
- ▲
request property
was restricted to a list of enum valuesrequest-property-became-enum
- ▲
the
//request property's minLength was increased from0to1request-property-min-length-increased
- ▲
the
request property's minLength was increased from0to1request-property-min-length-increased
- ▲
the
request property's minLength was increased from0to1request-property-min-length-increased
- ▲
the
/request property's minLength was increased from0to1request-property-min-length-increased
- ▲
the
/request property's minLength was increased from0to1request-property-min-length-increased
- ▲
the
//request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
//request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
//request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
//request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
//request property type changed fromnumbertointegerrequest-property-type-changed
- ▲
the
/request property format changed from no format touuidrequest-property-type-changed
- ▲
the
response's property format changed fromdatetodate-timefor statusresponse-property-type-changed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ●
removed the optional property
from the response with the statusresponse-optional-property-removed
- ○
added the new optional request property
new-optional-request-property
- ○
the request property
//became nullablerequest-property-became-nullable
- ○
the request property
became nullablerequest-property-became-nullable
- ○
the request property
became nullablerequest-property-became-nullable
- ○
the request property
became nullablerequest-property-became-nullable
- ○
the request property
became optionalrequest-property-became-optional
- ○
the
request property default valuetruewas removedrequest-property-default-value-removed
- ○
the
request property default valuetruewas removedrequest-property-default-value-removed
- ○
the
request property default value{"escalationType":"RUN_BASED","runBasedEscalation":{"failedRunThreshold":1},"reminders":{"amount":0,"interval":5},"parallelRunFailureThreshold":{"enabled":false,"percentage":10}}was removedrequest-property-default-value-removed
- ○
the
request property default value0was removedrequest-property-default-value-removed
- ○
the
request property default value10000was removedrequest-property-default-value-removed
- ○
the
request property default valuetruewas removedrequest-property-default-value-removed
- ○
the
request property default valuefalsewas removedrequest-property-default-value-removed
- ○
the
request property default valueRUN_BASEDwas removedrequest-property-default-value-removed
- ○
the
request property default value10was removedrequest-property-default-value-removed
- ○
the
request property default value5was removedrequest-property-default-value-removed
- ○
the
request property default valuefalsewas removedrequest-property-default-value-removed
- ○
the
request property default value20000was removedrequest-property-default-value-removed
- ○
the
request property default valuefalsewas removedrequest-property-default-value-removed
- ○
the
request property default value10was removedrequest-property-default-value-removed
- ○
the
request property default valuefalsewas removedrequest-property-default-value-removed
- ○
the
request property default valuefalsewas removedrequest-property-default-value-removed
- ○
the
request property default valuefalsewas removedrequest-property-default-value-removed
- ○
the
request property default valuetruewas removedrequest-property-default-value-removed
- ○
added the new
0.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
1.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
10.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
120.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
1440.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
15.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
180.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
2.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
30.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
360.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
5.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
60.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
720.00enum value to the request propertyrequest-property-enum-value-added
- ○
added the new
undefinedenum value to the request propertyrequest-property-enum-value-added
- ○
the
request property's maxLength was increased from500to510request-property-max-length-increased
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
- ○
added the non-success response with the status
response-non-success-status-added
This revision also has 566 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○
added the optional property
to the response with the statusresponse-optional-property-added
- ○