Retrieves a check session. Results may be incomplete if the check session is still in progress.
Once a check session has finished, results will include at least one check result for each run location: one result with resultType equal to "FINAL", and zero or more results with resultType equal to "ATTEMPT" (one for each failed attempt, if any).
Each result contains just enough information to quickly determine whether the check run was successful or not. To dive even deeper into individual results, use the GET /v1/check-results/{checkId}/{checkResultId} endpoint to retrieve detailed data about a specific result.
The status field may return CANCELLED for sessions cancelled via POST /v1/check-sessions/{checkSessionId}/cancel, and each per-result object includes an isCancelled boolean.
Documentation Index
Fetch the complete documentation index at: https://checklyhq.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
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]"
Your Checkly account ID, you can find it at https://app.checklyhq.com/settings/account/general
Check session ID.
Successful
AGENTIC, API, BROWSER, HEARTBEAT, ICMP, MULTI_STEP, TCP, PLAYWRIGHT, URL, DNS STARTED, PROGRESS, FAILED, PASSED, DEGRADED, PROGRESS_FAILED, PROGRESS_DEGRADED, TIMED_OUT, CANCELLED CLI_DEPLOY, DEPLOYMENT, DEPLOYMENT_CACHE_WARMER, EDITOR, GROUP_RUN_ALL, LEGACY_TRIGGER, SCHEDULER, SCHEDULE_NOW, TEST_NO_RECORD, TEST_RECORD, TRIGGER_NO_RECORD, TRIGGER_RECORD, TRIGGER_API, null