Key Takeaways
- Polar AccessLink API uses a transaction-based data model: you must open a transaction, fetch data within it, and commit or rollback before new data is available.
- HRV4T (Heart Rate Variability for Training) provides nightly HRV recordings taken in a standardized three-minute morning measurement, making the data consistent across users.
- Nightly Recharge is Polar's overnight recovery metric combining ANS (autonomic nervous system) charge from HRV analysis with sleep charge from sleep staging.
- Training Load Pro splits load into Cardio Load and Muscle Load, enabling coaching apps to understand not just how hard a user trained but what physiological systems were stressed.
- Developer access to Polar AccessLink is self-serve but requires users to grant consent through the Polar authorization flow before data is accessible.
- Open Wearables normalizes Polar data alongside other supported providers into a unified schema.
Introduction
Polar has been manufacturing heart rate monitors and sports watches since the 1970s and has built one of the most sophisticated training data models in the wearable industry. Their devices are disproportionately popular among endurance athletes, coaches and sports scientists who need precise physiological data rather than general wellness tracking.
The Polar AccessLink API exposes this data to developers. Unlike consumer-oriented platforms that abstract away complexity behind simple scores, Polar gives you the underlying measurements: raw RR interval data for HRV analysis, detailed training load breakdowns by cardiovascular and muscular demand, and sleep stages with autonomic nervous system state during recovery.
The trade-off is that the API has a non-standard transaction model that requires understanding before you can reliably fetch data, and the depth of available metrics means your normalization layer has real work to do. For apps serving serious athletes or building evidence-based coaching features, Polar is often the richest available data source.
What Polar AccessLink Provides
Training and exercise data covers over 100 sport types with detailed session summaries. Each session includes duration, distance for applicable sports, heart rate time series, heart rate zones, cadence for cycling and running, altitude data for GPS-enabled outdoor activities, Training Effect scores for aerobic and anaerobic adaptation, and Cardio Load and Muscle Load from Training Load Pro on supported devices.
Daily activity data includes step count, active calories, sedentary time, activity goal progress and activity time by intensity zone. Polar devices track movement throughout the day and report how much time the user spent at low, medium and high activity levels.
Sleep data includes total sleep time, sleep stages (light, deep and REM), sleep continuity scores, and breathing metrics on devices that support continuous heart rate monitoring during sleep. Sleep timing, sleep efficiency and wake episodes are also available.
Nightly Recharge is Polar's overnight recovery composite. It combines ANS Charge (derived from HRV analysis during the first hours of sleep, when parasympathetic nervous system activity provides the clearest recovery signal) and Sleep Charge (based on sleep staging, duration and continuity). Both components are scored individually and combined into an overall Nightly Recharge status.
HRV4T data is available on devices and plans where the user has enabled the morning HRV measurement. This is a standardized three-minute recording taken lying down immediately after waking, producing consistent RR interval data suitable for trend analysis. Polar's approach to HRV measurement reduces the variability that comes from measuring HRV continuously throughout the night.
Physical information includes VO2 max estimates, running performance tests, orthostatik test results and maximum heart rate, which are used in Polar's training load calculations and are available via the physical info endpoint.
Authentication and User Registration
Polar AccessLink uses OAuth 2.0 with the authorization code flow. Register your application at the Polar developer portal to receive client credentials. The process is self-serve and does not require an approval period.
There is a critical step that Polar requires before you can read any data for a user: after completing the OAuth authorization flow, you must explicitly register the user with your application via a POST to the AccessLink users endpoint. This registration step creates the association between the Polar user account and your application in Polar's system. If you skip this step, subsequent data requests will fail even with a valid access token.
Polar access tokens are long-lived and do not expire. This simplifies token management significantly compared to providers that require frequent refreshes. Store the access token securely per user and use it for all subsequent requests. If a user revokes access via the Polar Flow app or web service, the token becomes invalid and the user needs to re-authorize.
The Transaction Model
Polar AccessLink's transaction model is the most significant architectural difference from other wearable APIs. Data is not available via simple GET requests with date range parameters. Instead, you must work through a transaction lifecycle.
To fetch new training sessions, you open a transaction for the exercise resource, list the available sessions within the transaction, fetch each session by its transaction-specific ID, and then commit the transaction. Only after committing does Polar mark those sessions as delivered and make subsequent new sessions available in future transactions.
If you open a transaction and fail to commit (for example due to a processing error on your side), the same data will be available in the next transaction. This provides a form of at-least-once delivery guarantee. However, if you commit without successfully processing and storing the data, you will not be able to retrieve it again through the standard transaction flow.
Separate transactions exist for different resource types: exercises, daily activity, sleep and physical information each have their own transaction streams. You must manage each independently. A robust implementation opens, processes and commits each transaction type as part of a scheduled sync job, handles errors before committing, and stores raw response payloads before processing to enable reprocessing if your parsing logic changes.
HRV4T in Product Context
The standardized nature of HRV4T measurements makes them unusually valuable for building HRV-based features. Because every measurement is taken using the same protocol (three minutes, lying down, at the same time of day), the data is comparable across days and across users in a way that continuous overnight HRV is not.
This enables meaningful population-level analysis for coaching applications that serve multiple users. You can build personalized HRV baseline models using the user's own 60-90 day HRV history, flag days where morning HRV is more than one standard deviation below the user's baseline, and correlate HRV deviations with training load, sleep quality and life stress indicators.
For individual user features, HRV4T trend analysis over rolling 7 and 28 day windows is the foundation of readiness-based training recommendations. A declining HRV trend over 7 days against a rising cumulative training load is a strong signal for an unplanned recovery day regardless of how the user reports feeling.
Open Wearables and Polar
Open Wearables implements the Polar AccessLink transaction model, handles the mandatory user registration step, manages long-lived token storage, and normalizes Polar data into the same schema used for Garmin, Whoop, Samsung Health, Suunto, Ultrahuman, Oura, Google Health Connect and Apple HealthKit.
Polar-specific metrics like ANS Charge, Nightly Recharge and Training Effect are preserved in the normalized output as provider-specific extensions alongside the common fields (sleep duration, HRV, resting heart rate, workout distance and duration) that appear across all providers. Self-hosted, MIT licensed, no per-user fees.
FAQ
Which Polar devices support HRV4T?
HRV4T is available on Polar Vantage V2, Vantage M2, Ignite 2, Ignite 3, Pacer, Pacer Pro, Grit X2 Pro and other recent Polar devices. Older devices may not support the morning HRV measurement. Check Polar's device compatibility documentation for the current list.
What happens if a transaction is left open without being committed?
Polar will keep the transaction available but will not make new data accessible until the existing transaction is committed or rolled back. In practice, implement a rollback on any processing error, log the failure, and retry the transaction in the next sync cycle rather than leaving transactions open indefinitely.
Does Polar AccessLink support webhooks?
Polar AccessLink supports webhooks for new exercise notifications. When a user syncs a new workout from their device to Polar Flow, Polar can send a webhook to your configured endpoint. This reduces the need for constant polling but does not replace the transaction model: you still need to open and commit a transaction to actually fetch the exercise data after receiving the webhook.
Can I access historical data for a user who just connected?
Polar AccessLink provides access to data from the past 90 days at the time of user registration. Data older than 90 days is not available via the API. Plan your onboarding experience accordingly: inform users that their recent 90 days of data will be synced and do not promise access to older history.
How is Nightly Recharge different from Whoop's Recovery Score?
Both metrics measure overnight physiological recovery using HRV as a primary input, but they differ in methodology and output. Polar's Nightly Recharge separates ANS Charge (HRV-based) and Sleep Charge (sleep staging-based) and reports them as distinct components alongside a combined status. Whoop's Recovery Score is a single composite score combining HRV, resting heart rate, respiratory rate and sleep performance into a percentage. Polar's split gives more diagnostic information; Whoop's single score is simpler to surface in a UI.
Polar Integration
View the full Polar integration documentation on Open Wearables.
See Related Articles
How to Access Polar Watch Data in Your Health App
Garmin Connect API: Developer Guide for Activities and Health Metrics
Strava API Developer Guide: Activities, Heart Rate and GPS Data
