get_activity_report
Retrieve a report for one activity covering overview, plan vs execution, power meter check, climbs, and data quality in one call.
Instructions
Use first for any question about one activity: overview, plan vs execution, power meter check, climbs and data quality in one call (read-only, 3-4 API requests).
The overview has thresholds, device, sport-assigned custom fields, fueling, weather and W′ balance. With a paired event or planned_workout_doc the plan-vs-execution analysis follows (as analyze_workout_execution), otherwise the intervals; a second-power-meter check only with enough valid paired samples; climbs without intervals or above 500 m gain; then data-quality notes. compact = core numbers and up to 5 key findings. Full detail: get_activity_details, analyze_workout_execution, compare_power_streams, analyze_climbs, get_activity_data_audit. Methods: intervals://methods/activity-data, intervals://methods/execution (get_guide).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| activity_id | Yes | Activity id, e.g. i123456789 | |
| detail_level | No | compact = core numbers, up to 5 key findings, data-quality flags; standard = full analysis, at most 30 interval lines; full = everything, all custom fields and streams | standard |
| output_format | No | json = machine-readable, all fields | text |
| include_climbs | No | Force (true) or suppress (false) the climbs; default only without intervals or above 500 m gain | |
| pause_tolerance_s | No | Recording pause per step before it is flagged, seconds; default 60 | |
| start_tolerance_s | No | Plan timeline shift before a step is flagged, seconds; default 120 | |
| planned_workout_doc | No | Workout document {"steps": [...]} to compare against, e.g. when the event was deleted | |
| include_route_history | No | Add earlier activities on the same Intervals.icu route (2 extra requests) | |
| duration_tolerance_pct | No | Step duration tolerance in % before a step is split or flagged short; default 10 |