Get athlete profile: thresholds, HR/pace zones, FTP, weight, sport settings.

Call this first in a coaching session. Zone boundaries are needed to interpret every other number, and to write workouts with correct targets.

List completed activities with training load, HR and elevation.

Args: oldest: Start date YYYY-MM-DD. Defaults to days_back before today. newest: End date YYYY-MM-DD (inclusive). Defaults to today. days_back: Used only when explicit dates are omitted. activity_type: Optional filter, e.g. "Run", "Ride", "Hike", "WeightTraining". Matched case-insensitively.

Get one activity in detail, optionally with detected intervals/laps.

Use for post-session analysis: how each interval actually went, HR drift, and where elevation was gained. Activity ids look like "i55751783".

Get time-series streams for an activity, downsampled to ~200 points each.

Args: activity_id: e.g. "i55751783". types: Stream names. Defaults to heartrate, altitude, velocity_smooth, distance, cadence, grade_smooth. Others: watts, temp, latlng, time, moving, fixed_watts.

Returns min/max/mean plus a downsampled series per stream. Full per-second data is deliberately not returned: a long trail run is >10k samples per stream and the shape is what matters for coaching, not every sample.

Get daily wellness: HRV, resting HR, sleep, weight, CTL/ATL, soreness.

This is the autoregulation input. Check it before prescribing a hard session, and compare HRV and resting HR against the athlete's own recent baseline rather than population norms.

List calendar events: planned workouts, notes and races.

Use before writing a new week so existing plan entries are not duplicated. Every event id returned here can be passed to delete_planned_workout.

Create a structured planned workout on the Intervals.icu calendar.

Intervals.icu syncs planned workouts to a connected Garmin Connect account, so this is the path for getting a session onto the watch. See the README caveat: confirm the first workout actually reaches Garmin before relying on this in a training block.

Args: start_date: Local date YYYY-MM-DD. Time is forced to 00:00:00, which the API requires for calendar events. name: Short session title, e.g. "3x8min Schwelle". description: Workout in Intervals.icu syntax (see below). activity_type: "Run", "Ride", "Hike", "WeightTraining", "Swim". moving_time: Total duration in seconds. Optional; Intervals.icu derives it from the parsed description. target: "HR", "PACE" or "POWER". Use "HR" for trail and hiking work where pace is meaningless on steep terrain. training_load: Optional manual load override. external_id: Stable id of your own. Reusing it with the same date makes the call idempotent, so a re-planned week updates instead of duplicating.

Workout syntax — one step per line, prefixed "- ":

- 15m Z2 Warmup
3x
- 8m Z4
- 3m Z1
- 10m Z1 Cooldown

A bare "Nx" line on its own starts a repeated block; the following steps until the next blank line are repeated. Durations use m/s/h. Targets can be zones ("Z2"), ranges of threshold ("75-82%"), or free text for steps with no measurable target. Blank lines separate blocks.

Delete a calendar event by its numeric id (from list_planned_workouts).

Verify the API key works and report rate limit headroom.