Verifies the connection and fetches the athlete's threshold values.

Run this before building a workout. FTP, threshold heart rate and zone boundaries come from the account, so intensities are computed against the right numbers instead of a guess.

Puts a block of planned workouts in the intervals.icu calendar.

From there the workouts sync to Zwift (Workouts -> Custom -> Intervals.icu) and Garmin.

Write the block name, the workout names and the descriptions in ENGLISH, even when talking to the user in another language. The calendar, Zwift and Garmin are English, and these workouts outlive the conversation.

After the upload, the server's interpretation of each workout is compared with the duration you stated. That catches DSL mistakes that would otherwise be silent — above all nested repeats, which make the workout shorter than intended without the server complaining. Read the warnings: a workout can upload without errors and still be wrong.

Re-run with the same block_name to correct; it creates no duplicates.

Shows workouts this server has put in the calendar during a period.

Shows only its own workouts. Anything you added by hand, imported, or got from a coach is invisible here — and cannot be deleted by delete_block either.

Removes a block from the calendar.

Deletes only workouts this server created under the given block name. Workouts you added yourself, imported, or that belong to another block cannot be hit.

Downloads an uploaded block as workout files.

The workouts must be in the calendar first — run upload_block before. The files are an alternative to the intervals.icu integration, useful when Zwift runs on a device where the integration is unavailable.

.zwo files are used in Zwift by placing them under Documents/Zwift/Workouts// and appear under Workouts -> Custom.

Reviews planned versus actual training in a period.

Shows this server's planned workouts with their outcome — the paired activity and its server-computed compliance — flags missed workouts, and lists every other activity in the window: spontaneous rides and foreign plans count toward load all the same. Defaults to the last 7 days.

The numbers are reported, not interpreted — the judgement about what they mean for the next block is yours. Use get_activity for the per-interval detail of one ride, get_fitness for the CTL/ATL/form trend.

Fetches one completed activity with its intervals.

The per-rep actuals — watts, heart rate, cadence per detected interval — for checking how a structured workout actually went. Run review_period first to find the activity id.

Shows the fitness trend: CTL, ATL and form (TSB) per day.

Form is computed here as CTL − ATL — intervals.icu exposes no form field. Defaults to the last 28 days. The trend says whether the athlete is peaking or digging a hole; what to do about it is the caller's judgement.

Shows the athlete's power curve — best average power per duration.

The strength profile of a cyclist: best 5 s, 1 min, 5 min, 20 min and longer efforts over the period, in watts and W/kg. Downsampled to the classic durations; the raw curve carries one point per second.