Overview
The Analytics endpoints expose the same monitoring data that powers your dashboard: pre-computed metric aggregations, raw executions, availability samples, incidents and anomalies. They all require an API key withanalytics: read (see Authentication) and are automatically scoped to the connections your key can access.
Base URL:
Cursor Pagination
The read endpoints use keyset (cursor) pagination rather than offsets — stable even as new rows arrive.
Every response carries a
pagination object:
next_cursor back as cursor. When has_more is false, you’ve reached the end.
Metric Aggregations
Parameters
Valid
metric_type values:
daily_executions, daily_success_rate, daily_avg_duration, weekly_executions, weekly_success_rate, weekly_avg_duration, monthly_executions, monthly_success_rate, monthly_avg_duration, daily_availability, weekly_availability, monthly_availability, monthly_openclaw_cost
Executions
Availability
Availability Summary
Incidents
availability, missed_heartbeat, anomaly, budget; lifecycle open → acknowledged → resolved). Supports connection_id, since / until and cursor pagination.
Anomalies
connection_id, since / until and cursor pagination.
Related
Analytics in the app
How this data is visualized in the dashboard
Usage & Cost API
Push and query AI token usage and cost

