Overview
This endpoint returns detailed execution results for a specific check. Check results contain comprehensive information about each check execution including response times, status codes, error details, and performance metrics.Response Example
Query Parameters
Time Range Filters
Time Range Filters
from(string): Start date for results (ISO 8601 format)to(string): End date for results (ISO 8601 format)period(string): Predefined time period (1h, 6h, 24h, 7d, 30d)
Filtering Options
Filtering Options
status(string): Filter by result status (success, failed)location(string): Filter by monitoring locationtriggeredBy(string): Filter by trigger type (schedule, api, manual)responseTimeMin(integer): Minimum response time in millisecondsresponseTimeMax(integer): Maximum response time in milliseconds
Pagination & Sorting
Pagination & Sorting
page(integer): Page number (default: 1)limit(integer): Number of results per page (default: 10, max: 100)sortBy(string): Sort field (startedAt, duration, responseTime)sortOrder(string): Sort order (asc, desc, default: desc)includeSummary(boolean): Include summary statistics (default: true)
Result Status Types
| Status | Indicates | Characteristics | Common Causes |
|---|---|---|---|
| Success | • All assertions passed • HTTP status codes in success range • No execution errors occurred • Response received within timeout | • Status code typically 2xx • All defined assertions evaluate to true • Complete response received • Execution completed normally | N/A |
| Failed | • One or more assertions failed • HTTP error status codes (4xx, 5xx) • Network or timeout errors • Script execution errors | • Status code in error range • Assertions evaluate to false • Incomplete or missing response • Execution terminated abnormally | • API returning error status codes • Assertion mismatches • Network connectivity issues • Timeout exceeded |
Response Time Breakdown
Timing Components
Timing Components
DNS Resolution (
timing.dns)- Time to resolve domain name to IP address
- Typically 0-50ms for cached results
- Higher values may indicate DNS issues
timing.tcp)- Time to establish TCP connection
- Includes network latency
- Geographic distance affects this timing
timing.tls)- Time for SSL/TLS negotiation
- Only present for HTTPS requests
- Certificate validation time included
timing.firstByte)- Time from request sent to first response byte
- Server processing time
- Most critical for API performance analysis
timing.download)- Time to download response body
- Affected by response size and bandwidth
- Usually minimal for API responses
Performance Analysis
Performance Analysis
Use timing breakdown to identify bottlenecks:
Common Use Cases
Performance Monitoring
Track API performance trends and identify regressions
Debugging Failed Checks
Investigate check failures with detailed error analysis
SLA Compliance Reporting
Generate uptime and compliance reports for stakeholders
Geographic Performance Analysis
Compare performance across different monitoring locations
Additional Use Cases
Performance Monitoring
Performance Monitoring
Track API performance over time:
- Monitor response time trends
- Identify performance regressions
- Track timing component changes
- Set up performance baselines
Debugging Failed Checks
Debugging Failed Checks
Investigate check failures in detail:
- Examine error messages and stack traces
- Analyze failed assertions
- Review request/response details
- Identify patterns in failures
SLA Compliance Reporting
SLA Compliance Reporting
Generate compliance reports:
- Calculate uptime percentages
- Track SLA violations
- Generate compliance dashboards
- Export data for stakeholder reports
Geographic Performance Analysis
Geographic Performance Analysis
Compare performance across locations:
- Identify regional performance differences
- Optimize global infrastructure
- Monitor CDN effectiveness
- Plan capacity expansion
Additional Examples
Check results provide detailed execution data for performance analysis, debugging, and compliance reporting. The timing breakdown helps identify bottlenecks in different components of the request lifecycle.