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
Path Parameters
Query Parameters
Limit the number of results
1 <= x <= 100
Page number
Select documents up from this UNIX timestamp (>= date). Defaults to now - 6 hours.
Optional. Select alerts up to this UNIX timestamp (< date). Defaults to 6 hours after "from".
Response
Successful
The name of the check.
"API Check"
The unique ID of this alert.
"1"
The ID of check this alert belongs to.
"db147a95-6ed6-44c9-a584-c5dca2db3aaa"
The type of alert.
NO_ALERT
, ALERT_FAILURE
, ALERT_FAILURE_REMAIN
, ALERT_FAILURE_DEGRADED
, ALERT_RECOVERY
, ALERT_DEGRADED
, ALERT_DEGRADED_REMAIN
, ALERT_DEGRADED_FAILURE
, ALERT_DEGRADED_RECOVERY
, ALERT_SSL
"ALERT_FAILURE"
The type of the check.
API
, BROWSER
, HEARTBEAT
, MULTI_STEP
, TCP
, PLAYWRIGHT
, URL
, DNS
"API"
What data center location this check alert was triggered from.
"us-east-1"
Describes the time it took to execute relevant parts of this check. Any setup timeor system time needed to start executing this check in the Checkly backend is not part of this.
10
Any specific error messages that were part of the failing check triggering the alert.
"OK"
The status code of the response. Only applies to API checks.
"200"
The date and time this check alert was created.
The date and time this check alert was started.