Skip to main content
GET
/
v1
/
check-results
/
{checkId}
Lists all check results
curl --request GET \
  --url https://api.checklyhq.com/v1/check-results/{checkId} \
  --header 'Authorization: <api-key>'
[
  {
    "id": "<string>",
    "name": "<string>",
    "checkId": "<string>",
    "hasFailures": true,
    "hasErrors": true,
    "isDegraded": true,
    "overMaxResponseTime": true,
    "runLocation": "<string>",
    "startedAt": "2023-11-07T05:31:56Z",
    "stoppedAt": "2023-11-07T05:31:56Z",
    "created_at": "2023-11-07T05:31:56Z",
    "responseTime": 123,
    "apiCheckResult": {
      "assertions": [
        {
          "source": "STATUS_CODE",
          "target": 200
        }
      ],
      "request": {
        "method": "GET",
        "url": "https://api.checklyhq.com",
        "data": "",
        "headers": {},
        "params": {}
      },
      "response": {
        "status": 200,
        "statusText": "OK",
        "body": "<title> Checkly Public API </title>",
        "headers": {},
        "timings": {},
        "timingPhases": {}
      },
      "requestError": "null",
      "jobLog": {},
      "jobAssets": "null"
    },
    "browserCheckResult": "null",
    "multiStepCheckResult": "null",
    "checkRunId": 123,
    "attempts": 123,
    "resultType": "FINAL",
    "sequenceId": "2dbfa2a3-5477-45ea-ac33-ee55b8ea66ff"
  }
]

Authorizations

​
Authorization
string
header
required

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

​
x-checkly-account
string

Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general

Path Parameters

​
checkId
string
required

Query Parameters

​
limit
integer
default:10

Limit the number of results

Required range: 1 <= x <= 100
​
page
number
default:1

Page number

​
from
string<date>

Select documents up from this UNIX timestamp (>= date). Defaults to now - 6 hours.

​
to
string<date>

Optional. Select alerts up to this UNIX timestamp (< date). Defaults to 6 hours after "from".

​
location
enum<string>

Provide a data center location, e.g. "eu-west-1" to filter by location

Available options:
us-east-1,
us-east-2,
us-west-1,
us-west-2,
ca-central-1,
sa-east-1,
eu-west-1,
eu-central-1,
eu-west-2,
eu-west-3,
eu-north-1,
eu-south-1,
me-south-1,
ap-southeast-1,
ap-northeast-1,
ap-east-1,
ap-southeast-2,
ap-southeast-3,
ap-northeast-2,
ap-northeast-3,
ap-south-1,
af-south-1
​
checkType
enum<string>

The type of the check

Available options:
API,
BROWSER,
HEARTBEAT,
MULTI_STEP,
TCP,
PLAYWRIGHT,
URL,
DNS
​
hasFailures
boolean

Check result has one or more failures

​
resultType
enum<string>
default:FINAL

The check result type (FINAL,ATTEMPT,ALL)

Available options:
FINAL,
ATTEMPT,
ALL

Response

Successful

​
resultType
enum<string>
default:FINAL
required

The type of result. FINAL means this is the final result of the check run. ATTEMPT means this is a result of a double check attempt.

Available options:
FINAL,
ATTEMPT,
ALL
Example:

"FINAL"

​
id
string

The unique ID of this result.

​
name
string

The name of the check.

​
checkId
string

The ID of the check.

​
hasFailures
boolean

Describes if any failure has occurred during this check run. This is should be your mainmain focus for assessing API or browser check behaviour. Assertions that fail, timeouts or failing scripts all resolve tothis value being true.

​
hasErrors
boolean

Describes if an internal error has occured in Checkly's backend. This should be false in almost all cases.

​
isDegraded
boolean

A check is degraded if it is over the degradation limit set by the "degradedResponseTime" field on the check. Applies only to API checks.

​
overMaxResponseTime
boolean

Set to true if the response time is over the limit set by the "maxResponseTime" field on the check. Applies only to API checks.

​
runLocation
string

What data center location this check result originated from.

​
startedAt
string<date-time>
​
stoppedAt
string<date-time>
​
created_at
string<date-time>
​
responseTime
number

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.

​
apiCheckResult
object

The response data for an API check.

​
browserCheckResult
object

The response data for a browser check.

Example:

null

​
multiStepCheckResult
object

The response data for a multi-step check.

Example:

null

​
checkRunId
number

The id of the specific check run that created this check result.

​
attempts
number

How often this check was retried. This will be larger than 0 when double checking is enabled.

​
sequenceId
string

The sequence ID of the check run. This is used to group check runs with multiple attempts together.

Example:

"2dbfa2a3-5477-45ea-ac33-ee55b8ea66ff"

⌘I