Overview
Create a new check group to organize related checks and apply shared settings. Check groups help you manage multiple checks efficiently by providing common configuration, environment variables, and alert channels.Request Example
Response Example
Configuration Options
Basic Settings
Basic Settings
name
(string): Display name for the check group
activated
(boolean): Whether checks in this group are active (default: true)muted
(boolean): Whether alerts are muted (default: false)tags
(array): Tags for organization and filteringlocations
(array): Default monitoring locations for checksfrequency
(integer): Default check frequency in minutes
Environment Variables
Environment Variables
locked
: true means the value is encrypted and masked in responses
Setup and Teardown Scripts
Setup and Teardown Scripts
- Runs before each check execution
- Can prepare test data or environment
- Available to all checks in the group
- Runs after each check execution
- Can clean up resources or log results
- Executes regardless of check success/failure
Alert Settings
Alert Settings
RUN_BASED
: Alert after N failed runsTIME_BASED
: Alert after failing for N minutes
- Monitor SSL certificates in the group
- Set days before expiration to alert
- Send follow-up alerts if issues persist
- Configure frequency and count
Code Examples
Best Practices
Naming Convention
Naming Convention
- The purpose or service being monitored
- The environment (production, staging)
- The type of checks (API, UI, health)
- “Production Payment API”
- “Staging User Authentication”
- “E-commerce Checkout Flow”
Environment Variables
Environment Variables
- Use environment variables for URLs, API keys, and configuration
- Mark sensitive values as
locked: true
- Use consistent naming conventions across groups
- Consider using different groups for different environments
Alert Configuration
Alert Configuration
- Set appropriate escalation thresholds based on criticality
- Use different alert channels for different severity levels
- Configure reminders for persistent issues
- Enable SSL certificate monitoring for HTTPS endpoints
Setup and Teardown Scripts
Setup and Teardown Scripts
- Keep scripts focused and lightweight
- Use setup scripts for common test data preparation
- Use teardown scripts for cleanup and logging
- Test scripts thoroughly before deployment
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
Query Parameters
Determines whether a new check will automatically be added as a subscriber to all existing alert channels when it gets created.
Body
The name of the check group.
"Check group"
Determines if the checks in the group are running or not.
Determines if any notifications will be send out when a check in this group fails and/or recovers.
Tags for organizing and filtering checks.
["production"]
An array of one or more data center locations where to run the checks.
["us-east-1", "eu-central-1"]
Determines how many checks are invoked concurrently when triggering a check group from CI/CD or through the API.
x >= 1
{
"url": "https://api.example.com/v1",
"headers": [
{
"key": "Cache-Control",
"value": "no-store"
}
],
"queryParameters": [{ "key": "Page", "value": "1" }],
"assertions": [
{
"source": "STATUS_CODE",
"comparison": "NOT_EMPTY",
"target": "200"
}
],
"basicAuth": {
"username": "admin",
"password": "abc12345"
}
}
The runtime version, i.e. fixed set of runtime dependencies, used to execute checks in this group.
2025.04
, 2024.09
, 2024.02
, 2023.09
, 2023.02
, 2022.10
50
[Deprecated] Retry failed check runs. This property is deprecated, and retryStrategy
can be used instead.
When true, the account level alert setting will be used, not the alert setting defined on this check group.
Alert settings.
List of alert channel subscriptions.
[]
An ID reference to a snippet to use in the setup phase of an API check in this group.
null
An ID reference to a snippet to use in the teardown phase of an API check in this group.
null
A valid piece of Node.js code to run in the setup phase of an API check in this group.
null
A valid piece of Node.js code to run in the teardown phase of an API check in this group.
null
An array of one or more private locations where to run the checks.
["data-center-eu"]
When true, the checks in the group will run in parallel in all selected locations.
The strategy to determine how failed checks are retried.
Response
Created
The name of the check group.
"Check group"
Determines if the checks in the group are running or not.
Determines how many checks are invoked concurrently when triggering a check group from CI/CD or through the API.
x >= 1
1
Determines if any notifications will be send out when a check in this group fails and/or recovers.
Tags for organizing and filtering checks.
["production"]
An array of one or more data center locations where to run the checks.
["us-east-1", "eu-central-1"]
50
[Deprecated] Retry failed check runs. This property is deprecated, and retryStrategy
can be used instead.
When true, the account level alert setting will be used, not the alert setting defined on this check group.
Alert settings.
List of alert channel subscriptions.
An ID reference to a snippet to use in the setup phase of an API check in this group.
null
An ID reference to a snippet to use in the teardown phase of an API check in this group.
null
A valid piece of Node.js code to run in the setup phase of an API check in this group.
null
A valid piece of Node.js code to run in the teardown phase of an API check in this group.
null
The runtime version, i.e. fixed set of runtime dependencies, used to execute checks in this group.
2025.04
, 2024.09
, 2024.02
, 2023.09
, 2023.02
, 2022.10
null
An array of one or more private locations where to run the check.
["data-center-eu"]
The strategy to determine how failed checks are retried.
When true, the checks in the group will run in parallel in all selected locations.