Overview
This endpoint provides detailed analytics for API checks, including response times, success rates, error rates, and other performance metrics over time. This data is essential for understanding the performance trends of your API endpoints.Response Example
Query Parameters
Time Range Filters
Time Range Filters
from
(string): Start date for analytics data (ISO 8601 format)to
(string): End date for analytics data (ISO 8601 format)period
(string): Predefined time period (24h, 7d, 30d, 90d)
Aggregation Options
Aggregation Options
granularity
(string): Data point granularity (5m, 15m, 1h, 1d)locations
(array): Filter by specific monitoring locationsincludeTimeline
(boolean): Include detailed timeline data (default: true)
Metrics Explained
Response Time Metrics
- Average Response Time: Mean response time across all requests
- P95 Response Time: 95th percentile response time
- P99 Response Time: 99th percentile response time
Success Metrics
- Success Rate: Percentage of successful requests (HTTP 2xx)
- Error Rate: Percentage of failed requests
- Total Requests: Total number of check executions
Geographic Breakdown
- Location Performance: Response times by monitoring location
- Regional Success Rates: Success rates per geographic region
- Request Distribution: How requests are distributed across locations
Trend Analysis
- Timeline Data: Minute-by-minute or hourly performance data
- Performance Trends: Identify performance degradation patterns
- Anomaly Detection: Spot unusual response time spikes
Use Cases
Performance Monitoring
Performance Monitoring
- Monitor average response times across different time periods
- Identify peak usage times and performance degradation
- Compare performance across different monitoring locations
- Set up alerts based on response time thresholds
SLA Compliance
SLA Compliance
- Track success rates against SLA targets
- Monitor P95 and P99 response times for SLA compliance
- Generate reports for stakeholders and customers
- Identify trends that might impact SLA compliance
Capacity Planning
Capacity Planning
- Analyze request volume trends over time
- Identify peak usage periods for scaling decisions
- Monitor performance impact of traffic increases
- Plan infrastructure upgrades based on growth trends
Geographic Performance
Geographic Performance
- Compare response times across different regions
- Identify geographic areas with performance issues
- Make decisions about CDN or additional infrastructure
- Optimize API routing based on geographic performance
Code Examples
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
Path Parameters
Query Parameters
Custom start time of reporting window in unix timestamp format. Setting a custom "from" timestamp overrides the use of any "quickRange".
Custom end time of reporting window in unix timestamp format. Setting a custom "to" timestamp overrides the use of any "quickRange".
Preset reporting windows are used for quickly generating report on commonly used windows. Can be overridden by using a custom "to" and "from" timestamp.
last24Hours
, last7Days
, last30Days
, thisWeek
, thisMonth
, lastWeek
, lastMonth
The time interval to use for aggregating metrics in minutes. For example, five minutes is 5, 24 hours is 1440.
1 <= x <= 43200
Filter based on whether a check result was either failing or passing
Determines how the series data is grouped. Note that grouped queries are a bit more expensive and might take longer.
runLocation
, statusCode
Available metrics for API Checks. You can pass multiple metrics as a comma separated string.
Limit the number of results
1 <= x <= 100
Page number