Summary
There is a single call meant to be your first one.
The training summary returns an aggregated coaching snapshot, and the vendor's own tool table says to start there. Behind it sit the specifics — recovery with HRV and resting heart rate, sleep by stage, cycle strain, workouts by zone — each with a range version for looking at a week rather than a day.
What it is
A read-only server over your own Whoop data, running locally against a Whoop developer application you register yourself.
What you get
- whoop_get_training_summary — an aggregated coaching snapshot, which the vendor marks as the place to start
- whoop_get_latest_recovery and whoop_get_recovery_range — the most recent recovery score, HRV, resting heart rate and SpO2, or a date range of them
- whoop_get_latest_sleep and whoop_get_sleep_range — the last sleep session with its stage breakdown, or a range
- whoop_get_latest_strain and whoop_get_strain_range — current cycle strain with average and maximum heart rate and kilojoules, or strain over past days with an average
- whoop_get_workouts — workouts with sport id, strain and heart-rate zones
- whoop_get_profile — profile and body measurements
- whoop_check_auth — confirms the stored tokens are valid and unexpired
Requirements
A Whoop developer account with a registered application, its client id and secret, and a one-time browser authorisation that stores encrypted tokens on your machine. Python, and the application's redirect URI set to the local callback the setup script listens on.