Polar API Integration Guide 2026: AccessLink Explained
CTO & Co-Founder
CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Yes, the Polar API, called AccessLink, lets you connect Polar data to your product, and it is free today. You create a client yourself, accept Polar's licence, and can start pulling data the same day. The rule that decides most projects is the data window: most data is only available for the last 28 days, and exercises for the last 30, so you must sync daily or lose history. Read the licence too, because it bans services that compete with Polar and lets Polar end your access with immediate effect.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
Polar integration at a glance
| Question | Short answer |
|---|---|
| Official API? | Yes. AccessLink API v3, REST with OAuth 2.0 and webhooks. |
| Cost to the developer? | Free at the moment. Polar says it can charge fees later at its discretion. |
| Does the end user need a subscription or device? | They need a Polar device and a Polar Flow account. A paid subscription requirement is not published. |
| Same-day start? | Yes. No approval step or wait time is described. |
| Who approves scale-up? | No approval tier is published. Rate limits grow with your user count. |
| HIPAA or BAA? | Not published. Plan as if no BAA is available. |
| Raw or summary data? | Both. Continuous heart rate, activity samples and exercise files, plus daily and sleep summaries. |
| First build | About 2 weeks for a working integration. This is our estimate. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| AccessLink cloud REST API | No | Yes | Click-through licence only | No | After the watch syncs to Polar Flow | Exercises, activity, continuous heart rate, sleep, Nightly Recharge, cardio load, Elixir biosensing results | Data older than 28 to 30 days | Most products |
| Webhooks (push) | No | Yes, public HTTPS endpoint | No | No | Notice when new data lands, then you pull | Events: EXERCISE, SLEEP, CONTINUOUS_HEART_RATE, SLEEP_WISE_CIRCADIAN_BEDTIME, SLEEP_WISE_ALERTNESS, ACTIVITY_SUMMARY, PHYSICAL_INFORMATION. Each payload is signed with HMAC SHA-256 in the Polar-Webhook-Signature header. Your endpoint must answer the PING with 200 OK. | The data itself. You still fetch it. Polar turns the webhook off after 7 days of failed deliveries. | Keeping in sync without polling |
| Exercise file export (FIT, TCX, GPX) | No | Yes | No | No | Same as the API | Per-exercise workout files | Sleep, daily activity | Training and sports medicine tools |
| Phone SDK | Not published for health data. | |||||||
| Apple Health or Health Connect | Polar Flow writes to both and reads nothing back from Apple Health. Apple Health gets sleep times, steps and workouts with heart rate and energy samples, but not continuous heart rate. Health Connect gets more: calories, distance, exercise with routes, heart rate, SpO2, resting heart rate, sleep stages, steps, VO2 max and weight. | |||||||
| Aggregators, checked 10 November 2026 | Terra, Junction, Thryve and ROOK list Polar as a cloud API source. Thryve says no historic data. Spike lists it with no route stated. Validic and Sahha coverage is not published. | |||||||
Clinical buyers should use the AccessLink API with webhooks and store every record on their own side as it arrives, since the API only serves the last 28 days for most data. Wellness and training apps can use the same route and add FIT files when they need full workout detail. Check the licence first if your product could be seen as an alternative to Polar Flow.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose AccessLink client? | Yours | Depends on the aggregator. Ask whether you get your own client. | Yours. We build it in your account. |
| Competing-service clause | Your counsel reads it | Your counsel and the aggregator's terms both apply | Your counsel reads it. We design the product around the answer. |
| Webhooks and the 28-day window | You build the webhook, signature check and daily pull | The aggregator runs them. Thryve says it gets no historic Polar data. | We build them, then hand them to you or run them |
| Data model | Polar's own fields | The aggregator's schema | FHIR Observations for your EHR or remote monitoring stack |
| Other devices later | One new build per device | Many devices through one API | Same pattern reused across devices |
| Time to first real user | Depends on your team | Depends on the aggregator's onboarding | About 2 weeks of build in our estimate, 3 for healthcare, as in the timeline below |
| Cost shape | Engineering time. AccessLink is free today. | Aggregator fee. Pricing for Polar on these platforms is not published. | Project fee, scoped after a call |
What data you can get
| Data | Granularity | History window | Push or pull |
|---|---|---|---|
| User and physical info | Profile values | Current | Pull |
| Exercises | Per session, with FIT, TCX or GPX files | Last 30 days uploaded to Flow | Pull |
| Daily activity and activity samples | Daily summary plus samples | Default last 28 days. You can ask from a date up to 365 days back, with a range of 28 days at most. | Pull |
| Continuous heart rate | Time series by date or range | Not published in the v3 reference (read 11 Nov 2026) | Pull |
| Cardio load | Daily | Last 28 days, plus history by days or months | Pull |
| Sleep (Sleep Plus, Sleep Plus Stages) | Per night | Last 28 days | Pull |
| Nightly Recharge (HRV, overnight heart rate) | Per night | Last 28 days | Pull |
| SleepWise alertness and circadian bedtime | Daily | Last 28 days, or a date range of 28 days at most | Pull |
| Elixir biosensing: body temperature, sleep skin temperature, skin contact, wrist ECG test results, SpO2 test results | Per measurement or test | Last 28 days or a 28-day range | Pull |
Everything is read by pull. Webhooks tell you new data is waiting for seven types: exercise, sleep, continuous heart rate, the two SleepWise types, activity summary and physical information. Nightly Recharge, cardio load and Elixir biosensing send no webhook, so pull those daily.
What is inside one Polar sleep and Nightly Recharge record
The sleep endpoint gives far more than a nightly score. These fields come from Polar's sleep and Nightly Recharge schemas.
| Field | What it holds |
|---|---|
| hypnogram | Sleep stage per 30-second epoch: 0 wake, 1 REM, 2 lighter non-REM, 3 light non-REM, 4 deep non-REM, 5 unknown, for example from bad skin contact |
| heart_rate_samples (sleep) | 5-minute average heart rate in beats per minute, sometimes more often |
| light_sleep, deep_sleep, rem_sleep, sleep_cycles | Stage totals and the number of sleep cycles for the night |
| heart_rate_variability_avg | RMSSD in milliseconds over a 4-hour period starting 30 minutes after falling asleep |
| heart_rate_avg, beat_to_beat_avg, breathing_rate_avg | Same 4-hour period: beats per minute, milliseconds between beats, breaths per minute |
| hrv_samples, breathing_samples | Time series through the night, keyed by clock time |
| ans_charge, nightly_recharge_status | ANS charge from -10.0 to +10.0 against the user's last 28 days, and a status from 1 (very poor) to 6 (very good) |
Continuous heart rate comes as samples every 5 minutes and leaves out workout heart rate, which you read from the exercise with samples=true. Elixir results arrive in clear units: temperature_celsius, deviation_from_baseline_celsius, blood_oxygen_percent and, for wrist ECG, amplitude_mv samples with average_heart_rate_bpm and a quality level.
What you cannot get
- Exercises older than 30 days, and most other data older than 28 days.
- Data for users who have not accepted all of Polar's mandatory consents. The API returns 403 for them.
- A published history window for continuous heart rate.
- Older transaction-based endpoints for exercises, activity and physical info. They are deprecated.
- Any statement on HIPAA, a BAA, FDA status or where data is stored.
- A phone SDK for health data. Polar does not publish one. Apple Health, Health Connect and aggregator routes are covered in the strategy table above.
How to get access
- Create a Polar Flow account. You do this yourself, today.
- Log in to the AccessLink admin site, create a client and save the client ID and secret.
- Accept the Polar API Limited License Agreement. It asks for an accurate description of your software.
- Send each user through OAuth sign-in, then register that user through the API before you read any data.
Polar describes no review step and no waiting time.
From zero to your first Polar data in four steps
- Create a client. Log in at admin.polaraccesslink.com with your Polar Flow account, fill in your application details and note the client ID and secret.
- Connect a user. Send them to flow.polar.com/oauth2/authorization with response_type=code and your client_id. Swap the code for a token at polarremote.com/v2/oauth2/token within 10 minutes, using Basic auth with your client ID and secret.
- Register the user. Reads fail until you do this. member-id is your own identifier for the user.
curl -X POST https://www.polaraccesslink.com/v3/users \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ -H 'Authorization: Bearer <access-token>' \ -d '{"member-id": "User_id_999"}' - Pull, then listen. Read the last 28 days of sleep, Nightly Recharge and activity once, then create your single webhook at /v3/webhooks and save the signature_secret_key, since it is shown only once. Exercises are different: only those uploaded to Flow after registration come through, so the first sync has none.
Terms you must know
These come from the Polar API Limited License Agreement. Section numbers were not captured in our research, so check the clause text before you sign.
- Medical use: the agreement does not mention medical or diagnostic use. A healthcare product should ask Polar in writing. A wellness product that makes no medical claims is less exposed (our reading).
- PHI, HIPAA and BAA: nothing is published. A healthcare product should assume Polar will not sign a BAA and keep Polar as a data source the patient connects, with PHI handled only on your side. A wellness product that holds no PHI is not affected.
- Storage and deletion: you must delete data on the user's request or when the agreement ends. Both readers need a delete path from day one.
- AI training and data selling: not covered in our research. Ask before you train models on Polar data.
- Branding: you must credit Polar as the data source, and you cannot use Polar marks in marketing without consent.
- Competing products: you cannot build a service "similar to or competing with Polar Ecosystem", and the main purpose must extend the member's experience. In our reading this hits training and coaching apps hardest, and a clinical program is usually further from it. Ask Polar if in doubt.
- Termination: Polar can end access "for any or no reason, with immediate effect". A healthcare program should not depend on Polar as its only data source.
Cost and payment terms
The API is free today. The agreement says "At the moment Polar offers the use and activation of Polar API's free of charge" and that Polar can charge fees later. The licence is royalty-free and non-exclusive. No enterprise contract or per-user fee is published. End users need a Polar device. Aggregator pricing was not part of our research.
Use cases
Cardiac rehab and remote follow-up
The patient connects Polar once through OAuth in your portal. When the watch syncs, Polar sends a webhook. Your server pulls the new exercise and continuous heart rate, stores it, and writes heart rate Observations to the care team's record over FHIR. Data used: exercises, continuous heart rate, Nightly Recharge.
- Patient has not accepted Polar consents and you get 403. Fix: show a clear prompt to finish consent in Polar Flow.
- Webhook endpoint down for 7 days and Polar deactivates it. Fix: alert on failures and run a daily pull as backup.
- Patient stops syncing and data passes the 28-day window. Fix: flag users with no new data after a few days.
Sports medicine and training load
The athlete connects Polar. Each new exercise triggers a webhook, and you fetch the session and FIT file plus cardio load. Clinicians see load trends on an app screen. Data used: exercises, FIT files, cardio load.
- You need a season of history but only 30 days are available. Fix: tell users history starts at connection, or import their own exported files.
- The product looks like a Polar Flow replacement. Fix: review the competing-service clause before launch.
Sleep and recovery coaching
A coaching or employer wellness app reads Sleep Plus Stages, Nightly Recharge and SleepWise each morning and shows a recovery view. Data used: sleep, HRV, alertness.
- The watch syncs late, so the morning view is empty. Fix: show "waiting for your watch to sync" and refresh on the webhook.
- Polar logos in your marketing. Fix: credit Polar as the source only, without its marks.
Research studies
Participants connect during enrollment. Your server pulls activity, sleep and Elixir results such as skin temperature and SpO2 tests daily into the study database. Data used: activity samples, sleep, Elixir biosensing.
- Gaps when a daily job fails. Fix: backfill within the 28-day window and log missing days.
- Participant withdraws. Fix: delete their data as the agreement requires and record the deletion.
Polar data in an EHR or remote monitoring program
Most healthcare teams want Polar readings next to clinical data, not in a separate app. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Store each reading as it arrives, because the API forgets it after 28 days.
| Polar value | FHIR Observation | Code |
|---|---|---|
| Continuous heart rate sample (heart_rate) | Heart rate, beats per minute | LOINC 8867-4 |
| Daily steps (activity) | Number of steps | LOINC 55423-8 |
| SpO2 test result (blood_oxygen_percent) | Oxygen saturation by pulse oximetry, percent | LOINC 59408-5 |
| Body temperature (temperature_celsius) | Body temperature, degrees Celsius | LOINC 8310-5 |
| Nightly breathing rate (breathing_rate_avg) | Respiratory rate, breaths per minute | LOINC 9279-1 |
| Nightly HRV, Nightly Recharge, ANS charge, sleep score | Device-specific Observation | Your own code system. Polar HRV is RMSSD over a set 4-hour window, and the scores are Polar's own, so no standard code fits exactly. |
Keep the Polar ids on each Observation, such as the hashed exercise id and source_device_id, so you can find a record again for a delete request. Sleep skin temperature is a skin reading, so do not map it to the body temperature code.
Known blockers and gotchas
- 28-day window. Data rolls off. Sync daily and store everything yourself.
- User registration step. OAuth alone is not enough. Register the user through the API or reads fail.
- Authorization code reuse. Codes last 10 minutes and are single use. Reusing one revokes every token from it. Make the callback idempotent.
- One webhook per client. Route events inside your own service. The signing key is shown once, so store it at creation.
- Webhook deactivation. After 7 days of failed delivery Polar turns it off. Monitor it.
- 403 on missing consent. Treat it as a step the user must finish.
- Rate limits scale with users. With 1,000 registered users the formula gives 20,500 calls per 15 minutes and 105,000 per day. Spread backfills and back off on 429.
- Consumer-grade data. Polar data comes from consumer watches and sensors. Clinical teams should treat it as supporting trend data and say so in the protocol.
- Deprecated endpoints. Older transaction-based endpoints are deprecated. Build on the current ones.
Delivery timeline
Our estimate. No step depends on Polar beyond accepting the licence.
| Week | Work | Depends on Polar? |
|---|---|---|
| 1 | Create client, accept licence, OAuth flow, user registration, webhook with signature check | Licence acceptance only |
| 2 | Pull exercises, activity, sleep, Nightly Recharge and Elixir data, daily sync job, FHIR mapping | No |
| 3 (healthcare) | Legal review of medical use and PHI questions, consent and deletion flows | Yes, if you wait for Polar's written answers |
Questions to ask Polar before you sign
- Does the agreement allow use in a clinical or medical program, and will you confirm that in writing?
- Will you sign a BAA, or do you expect us to keep PHI entirely on our side?
- What is the history window for continuous heart rate?
- Can we train AI models on data users share with us?
- Would our product count as "similar to or competing with Polar Ecosystem"?
- How much notice will you give before charging fees or ending access?
- Do you offer a phone SDK, and which data do you write to Apple Health and Health Connect?
Other device integration guides
Polar is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.
- Oura API integration guide
- WHOOP API integration guide
- Garmin API integration guide
- Ultrahuman API integration guide
- Eight Sleep API integration guide
- Fitbit and Google Health API integration guide
- Apple Health API integration guide
- Health Connect API integration guide
- Samsung Health API integration guide
- Withings API integration guide
- Dexcom API integration guide
- FreeStyle Libre API integration guide
- COROS API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Talk to us
Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. We do not have a partnership with Polar. Book a call about your device integration.
For whoever builds this
- Base: AccessLink API v3. Latest changelog entry dated 13.01.2026.
- Auth: OAuth 2.0 authorization code, single scope
accesslink.read_all. Code expires in 10 minutes, single use, reuse revokes all tokens issued from it. Access tokens do not expire unless revoked (the exampleexpires_inis about one year). No refresh token is described. Non-user endpoints use client credentials with Basic auth. - After OAuth, register the user through the API before reading data. Users missing mandatory consents return 403.
- Rate limits: per 15 minutes, 500 + (users x 20). Per 24 hours, 5000 + (users x 100). Above that you get 429.
- Webhooks: one per client, signed with HMAC SHA-256 in the
Polar-Webhook-Signatureheader. The signing key is shown once. Deactivated after 7 days of failed delivery. - Windows: exercises 30 days. Daily activity default 28 days, from-date up to 365 days back, range at most 28 days. Sleep, Nightly Recharge, Elixir 28 days. Cardio load 28 days plus historical by days or months.
- Exercise files: FIT, TCX, GPX.
- FHIR mapping (LOINC checked in the NLM LOINC search, 11 Nov 2026): heart rate 8867-4, steps 55423-8, SpO2 59408-5, body temperature 8310-5, breathing rate 9279-1. Polar HRV is RMSSD, so do not use 80404-7, which is SDNN. Code RMSSD in your own code system. ECG results: pick the code per result type and verify.
- Avoid the deprecated transaction-based endpoints for exercises, activity and physical info.
Sources
- Polar Flow and Apple Health, https://support.polar.com/en/support/connecting_polar_flow_with_apple_health, read 10 November 2026.
- Polar Flow and Health Connect, https://support.polar.com/en/flow-app-health-connect, read 10 November 2026.
- Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
- Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
- Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
- ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
- Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
- Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
- Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
- Polar AccessLink API v3 documentation, https://www.polar.com/accesslink-api/, read 10 November 2026.
- Polar API Limited License Agreement, https://www.polar.com/en/legal/polar-api-agreement, read 10 November 2026.
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Polar have a public API?
Is the Polar API free?
How far back can I get Polar data?
Does Polar need to approve my app?
Will Polar sign a HIPAA BAA?
Can I use Polar data in a medical product?
What health data does the Polar API return?
Do Polar access tokens expire?
What are the Polar API rate limits?
How do Polar webhooks work?
Can my product compete with Polar Flow?
Do my users need a paid Polar subscription?
Which OAuth scope does the Polar AccessLink API use?
How much history do I get when a user first connects?
Which Polar data types send a webhook?
How do I see how close I am to the Polar rate limit?
What HRV does the Polar API return?
Can I get heart rate during workouts from continuous heart rate?


