Call this endpoint to await the completion of a check session. A successful response will be returned once the check session reaches its final state (i.e. when it passes or fails).
If the check session takes a long time to complete, the endpoint will return a timeout error code. You should keep calling the endpoint until you receive a successful response, or a non-timeout related error code. If using curl, its --retry option is suitable.
The successful response of this endpoint is equivalent to the GET /v1/check-sessions/{checkSessionId} endpoint’s response for a completed check session.
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]"
The unique identifier of the check session.
The maximum time to wait for completion, in seconds.
1 <= x <= 3030
Returned when the check session has finished running.
Returned when the check session has finished running.
The unique identifier of the check session.
"8166fa86-c9b4-4162-8541-d380c6c212d8"
A link to the check session.
"https://app.checklyhq.com/accounts/1397c172-1938-4973-a225-5862298e571a/checks/a4cd4ad9-4815-4a9e-92d2-0a7c562ee69a/check-sessions/8166fa86-c9b4-4162-8541-d380c6c212d8"
The ID of the check.
"a4cd4ad9-4815-4a9e-92d2-0a7c562ee69a"
API, BROWSER, MULTI_STEP, TCP, PLAYWRIGHT, URL, DNS "API"
The final status of the check session.
FAILED, PASSED, DEGRADED, TIMED_OUT "PASSED"
The date and time when the session started.
"2025-08-28T18:23:40.262Z"
The date and time when the session stopped.
"2025-08-28T18:28:40.993Z"
The time the check session took, in milliseconds.
300731
The run locations of the check session.
["us-east-1", "eu-central-1"]"Example API Check"
The results of the check session.