Retrieve a check result
Show details of a specific check result.
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
Response
Successful
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.
FINAL, ATTEMPT, ALL "FINAL"
OpenTelemetry trace ID associated with this check result. null when no trace was recorded for this run (e.g. tracing not enabled in the runner).
"a1b2c3d4e5f67890abcdef0123456789"
The unique ID of this result.
The name of the check.
The ID of the check.
Describes if any failure has occurred during this check run. This should be your main focus for assessing API or browser check behaviour. Assertions that fail, timeouts or failing scripts all resolve to this value being true.
Describes if an internal error has occurred in Checkly's backend. This should be false in almost all cases.
A check is degraded if it is over the degradation limit set by the "degradedResponseTime" field on the check. Applies only to API checks.
Whether the run was cancelled before completion.
Set to true if the response time is over the limit set by the "maxResponseTime" field on the check. Applies only to API checks.
What data center location this check result originated from.
Time the check spent producing its result, in milliseconds. For protocol checks this is the measured operation time (a subset of the run): request time for API and URL checks, connection time for TCP, resolution time for DNS, average latency for ICMP and TRACEROUTE, request timing for GRPC, and TLS handshake time for SSL. For browser, multi-step, Playwright and agentic checks it is the run wall-clock duration. Any setup or system time before the check starts executing is not included.
The response data for an API check.
The response data for a browser check.
null
The response data for a multi-step check.
null
The response data for an agentic check.
The response data for a Playwright check.
null
Failure-debug diagnostics for a traceroute check.
Failure-debug diagnostics for a gRPC check.
Failure-debug diagnostics for an SSL check.
The id of the specific check run that created this check result.
How often this check was retried. This will be larger than 0 when double checking is enabled.
The sequence ID of the check run. This is used to group check runs with multiple attempts together.
"2dbfa2a3-5477-45ea-ac33-ee55b8ea66ff"
IDs of the error groups associated with this check result. Always an array: empty when the result has no associated error groups, single-element when there is one (typical for API/URL/TCP/ICMP checks), or multi-element for Playwright and multistep checks that can produce multiple distinct errors per run. Use these IDs to fetch the corresponding error group via the error-groups endpoint.
["883af87b-ac7c-44e3-9376-b4bece04e788"]