Skip to main content

​
Overview

This endpoint returns all alerts that have been triggered by checks in your account. Check alerts are generated when checks fail, recover, or meet specific conditions defined in your alert configurations.

​
Response Example

{
  "data": [
    {
      "id": "alert_789123456",
      "checkId": "check_api_health",
      "checkName": "Production API Health Check",
      "checkType": "api",
      "alertType": "check_failure",
      "severity": "high",
      "status": "triggered",
      "message": "Check failed: HTTP 500 Internal Server Error",
      "triggeredAt": "2024-01-25T14:30:00.000Z",
      "resolvedAt": null,
      "duration": null,
      "location": {
        "id": "us-east-1",
        "name": "N. Virginia, USA"
      },
      "checkResult": {
        "id": "result_123456789",
        "responseTime": 5240,
        "statusCode": 500,
        "error": "Internal Server Error",
        "url": "https://api.production.com/health"
      },
      "alertChannel": {
        "id": "channel_email_prod",
        "name": "Production Team Email",
        "type": "email"
      },
      "escalationLevel": 1,
      "acknowledgedBy": null,
      "acknowledgedAt": null,
      "tags": ["api", "production", "critical"]
    },
    {
      "id": "alert_987654321",
      "checkId": "check_website_home",
      "checkName": "Homepage Browser Check",
      "checkType": "browser",
      "alertType": "check_recovery",
      "severity": "medium",
      "status": "resolved",
      "message": "Check recovered: Page load successful",
      "triggeredAt": "2024-01-25T13:15:00.000Z",
      "resolvedAt": "2024-01-25T13:17:30.000Z",
      "duration": 150000,
      "location": {
        "id": "eu-west-1",
        "name": "Ireland, Europe"
      },
      "checkResult": {
        "id": "result_987654321",
        "responseTime": 1850,
        "statusCode": 200,
        "pageLoadTime": 2.3,
        "url": "https://www.example.com"
      },
      "alertChannel": {
        "id": "channel_slack_dev",
        "name": "Development Team Slack",
        "type": "slack"
      },
      "escalationLevel": 0,
      "acknowledgedBy": {
        "id": "user_123",
        "name": "John Developer",
        "email": "john@example.com"
      },
      "acknowledgedAt": "2024-01-25T13:16:00.000Z",
      "tags": ["frontend", "homepage"]
    }
  ],
  "meta": {
    "currentPage": 1,
    "totalPages": 15,
    "totalItems": 147,
    "limit": 10,
    "hasMore": true
  }
}

​
Common Use Cases

Incident Response

Monitor and respond to active incidents in real-time
GET /v1/check-alerts?status=triggered&severity=high

SLA Monitoring

Track service level agreement compliance and uptime
GET /v1/check-alerts?period=30d&status=resolved

Performance Analysis

Analyze system performance trends and degradation patterns
GET /v1/check-alerts?alertType=performance_degradation

Alert Management

Manage alert lifecycle and team coordination
GET /v1/check-alerts?acknowledgedBy=null&severity=critical

​
Query Parameters

  • checkId (string): Filter alerts for a specific check
  • checkType (string): Filter by check type (api, browser, heartbeat, tcp, multistep)
  • alertType (string): Filter by alert type (check_failure, check_recovery, performance_degradation)
  • severity (string): Filter by severity level (low, medium, high, critical)
  • status (string): Filter by alert status (triggered, acknowledged, resolved)
  • location (string): Filter by monitoring location
Example:
?checkType=api&severity=high&status=triggered&limit=20
  • from (string): Start date for alerts (ISO 8601 format)
  • to (string): End date for alerts (ISO 8601 format)
  • period (string): Predefined time period (24h, 7d, 30d)
Example:
?from=2024-01-01T00:00:00Z&to=2024-01-31T23:59:59Z

​
Alert Types

Check Failure

Triggered when:
  • HTTP status codes indicate failure (4xx, 5xx)
  • Network timeouts or connection errors
  • Browser check script failures
  • Assertion failures in API checks
Common scenarios:
  • API endpoints returning 500 errors
  • Website pages failing to load
  • Database connection timeouts

Check Recovery

Triggered when:
  • Previously failing check returns to success
  • Performance returns to acceptable levels
  • Services come back online
Indicates:
  • System has self-recovered
  • Manual intervention was successful
  • Temporary issues have resolved

Performance Degradation

Triggered when:
  • Response times exceed thresholds
  • Success rates drop below limits
  • Core Web Vitals degrade
Examples:
  • API response time > 2 seconds
  • Page load time > 5 seconds
  • Success rate < 95%

Heartbeat Missing

Triggered when:
  • Expected heartbeat signals not received
  • Service health checks fail
  • Cron jobs or scheduled tasks miss
Indicates:
  • Service may be down
  • Scheduled process failed
  • Network connectivity issues

​
Alert Severity Levels

Characteristics:
  • Immediate attention required
  • Service completely unavailable
  • Business-critical functionality affected
  • Customer-facing impact
Examples:
  • Payment processing API down
  • Login system failure
  • Complete website outage
  • Database connectivity lost
Characteristics:
  • Significant service degradation
  • Major functionality impacted
  • Customer experience affected
  • SLA potentially breached
Examples:
  • Search functionality slow
  • File upload failures
  • Partial API outages
  • Major performance degradation
Characteristics:
  • Minor service degradation
  • Non-critical features affected
  • Backup systems available
  • Limited customer impact
Examples:
  • Slow loading times
  • Non-essential API errors
  • Secondary feature failures
  • Performance warnings
Characteristics:
  • Minimal impact
  • Information or warnings
  • Proactive notifications
  • Future potential issues
Examples:
  • SSL certificate expiring soon
  • Cache hit rate declining
  • Non-critical service restarts
  • Performance trending concerns

​
Use Cases

Monitor and respond to active incidents:
  • Get real-time alerts for failing checks
  • Track alert resolution times
  • Identify patterns in alert frequency
  • Coordinate team response efforts
Track service level agreement compliance:
  • Monitor uptime and availability alerts
  • Calculate MTTR (Mean Time To Recovery)
  • Generate SLA compliance reports
  • Identify SLA breach patterns
Analyze system performance trends:
  • Track performance degradation alerts
  • Identify recurring performance issues
  • Monitor seasonal performance patterns
  • Optimize based on alert frequency
Manage alert lifecycle and team coordination:
  • Acknowledge alerts to prevent duplicates
  • Track who is handling incidents
  • Monitor alert resolution times
  • Optimize alert configurations

​
Additional Examples

curl -X GET "https://api.checklyhq.com/v1/check-alerts?status=triggered&severity=high&limit=20" \
  -H "Authorization: Bearer cu_1234567890abcdef" \
  -H "X-Checkly-Account: 550e8400-e29b-41d4-a716-446655440000"
Check alerts provide real-time visibility into the health and performance of your monitored services. Use this endpoint to build incident response dashboards and automated alert management systems.