WHOOP API Integration Guide 2026: Access, Data, Terms
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, you can integrate WHOOP through the WHOOP API. The route is the WHOOP API v2, a free REST API with OAuth sign-in and webhooks, and you can connect your first 10 members the day you register. The API gives you summaries per day, sleep and workout, with no heart rate time series. The rule that decides most healthcare projects is in the terms: no medical device use, no medical advice, and no protected health information (PHI) without WHOOP's prior written consent.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.
WHOOP integration at a glance
| Question | Answer |
|---|---|
| Official API? | Yes. WHOOP API v2 (REST, OAuth 2.0, webhooks). |
| Cost to the developer | None today. Terms 9.1: access is "currently provided at no charge", with notice before any charge. |
| Does the end user need a subscription or device? | They need a WHOOP strap and account. Whether a lapsed membership blocks API data is not published. |
| Same-day start? | Yes. Sandbox tier, up to 10 members. |
| Who approves scale-up? | WHOOP, by hand, one tier at a time. From the Build tier on, you need 50% of your current limit connected before asking. Wait time not published. |
| HIPAA / BAA | No PHI without WHOOP's written consent (terms 1.8). WHOOP does not say the API meets HIPAA. BAA not published. |
| Raw or summary data? | Summary only: per cycle (day), sleep, workout, recovery. |
| First build | About 3 to 4 weeks to a working integration (our estimate). Scale-up depends on WHOOP. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Cloud REST API v2 | No. A web page for OAuth consent is enough. | Yes | No for 10 members. Yes, tier by tier, beyond that. | No | Not published. | Cycles, recovery, sleep, workouts, body, profile | Heart rate stream, raw sensors | Any product that needs daily WHOOP data |
| Webhooks | No | Yes, a public HTTPS endpoint | Same as REST | No | Event on create or update. Delay not published. | Sleep, recovery, workout updated and deleted events | Cycle and body measurement events | Keeping data fresh without polling |
| Healthcare Partner API | No | Yes, server to server | Yes. "available exclusively to WHOOP-approved healthcare partners". No public application process. | No | Not published | Lab order flow: requisitions, FHIR-based service requests, diagnostic reports | Not published | Lab and clinical partners WHOOP has chosen |
| Phone SDK | Not published. WHOOP's developer docs list no SDK. | |||||||
| Apple Health / Health Connect | Yes, the WHOOP app writes to both. Apple Health gets workouts, active energy, heart rate during activities, sleep, resting heart rate, respiratory rate, SpO2 and steps if turned on. Health Connect gets exercise, calories, steps, sleep, resting heart rate, respiratory rate and SpO2. HRV, Recovery and Strain are not written to Apple Health. Some Health Connect data depends on the membership tier. | |||||||
| Aggregators, checked 10 November 2026 | Terra, Junction and Thryve list WHOOP as a cloud API source. ROOK lists it with no route stated. Sahha has it in public beta, sandbox only. Spike lists it with no route stated. Validic coverage is not published. Pricing is not published by any of them. | |||||||
| Member data export | No | No | No | No | Manual | Whatever the export holds | Anything ongoing | One-off research pulls |
For a wellness or coaching product, use the REST API with webhooks. It is free and you can ship to 10 members this week. For a healthcare buyer, use the same route only for programs that stay outside medical device use and medical advice, and get WHOOP's written PHI consent before any data touches a chart. If your use case is lab ordering, ask WHOOP about the Healthcare Partner API directly, since you cannot apply for it online.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose WHOOP API app? | Yours | Depends on the aggregator | Yours. We build it in your account. |
| Storage clause risk | Your counsel reads 4.2(2) | Same clause applies. Ask the aggregator how it stays within it. | Your counsel reads it. We design storage around the answer. |
| Member tiers | You request each tier yourself, from 10 members up to Production | Depends on the aggregator's own WHOOP app | Your app, your tier requests. We prepare them. |
| Webhooks and token renewal | You build and run them | The aggregator runs them | We build them, then hand them to you or run them |
| Data model | WHOOP'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 3 to 4 weeks of build in our estimate, plus WHOOP tier reviews |
| Cost shape | Engineering time. The API is free today. | Aggregator fee. Pricing is not published. | Project fee, scoped after a call |
What data you can get
| Data | Fields | Granularity | History window | Push or pull |
|---|---|---|---|---|
| Cycle (WHOOP's day) | Strain, kilojoules, average and max heart rate, step count | One record per cycle | Not published | Pull only |
| Recovery | Recovery score, resting heart rate, HRV (RMSSD, ms), SpO2 %, skin temperature °C | One per cycle | Not published | Pull, plus webhook |
| Sleep | Light, slow wave, REM and awake time, respiratory rate, sleep performance, consistency, efficiency | One per sleep | Not published | Pull, plus webhook |
| Workout | Strain, average and max heart rate, time in zones 0 to 5 | One per workout | Not published | Pull, plus webhook |
| Body measurement | Height, weight, max heart rate | Current value | Current only | Pull only |
| Profile | Basic profile, plus a call to revoke access | Current value | n/a | Pull only |
What is inside one WHOOP sleep record
The sleep endpoint returns one summary per sleep, not a stage timeline. These fields come from the Sleep model in WHOOP's OpenAPI spec.
| Field | What it holds |
|---|---|
| start, end, timezone_offset | Time bounds of the sleep, plus the member's offset at the time |
| nap | True if the sleep was a nap |
| score_state | SCORED, PENDING_SCORE or UNSCORABLE. Score values are present only when SCORED. |
| stage_summary | Total time in bed, awake, light, slow wave and REM sleep, plus time with no data, all in milliseconds. Also sleep cycle count and disturbance count. |
| sleep_needed | Baseline need, plus extra need from sleep debt and recent strain, and a reduction from recent naps, in milliseconds |
| respiratory_rate | Respiratory rate during the sleep |
| sleep_performance, consistency and efficiency percentages | 0 to 100. Performance and consistency may be missing if WHOOP lacks enough data. |
Recovery adds hrv_rmssd_milli (HRV by RMSSD, in milliseconds), resting heart rate, and spo2_percentage and skin_temp_celsius, which the spec says are present only for members on WHOOP 4.0 or later. A workout adds percent_recorded, the share of heart rate data WHOOP received, plus distance and altitude when sent to WHOOP. Cycles gained step_count on 23 Sep 2026, under the existing read:cycles scope.
What you cannot get
- Heart rate time series. There is no minute-level or beat-level endpoint.
- Raw sensor data. The API reference lists no raw data endpoint.
- Webhooks for cycles or body measurements. You must poll for those.
- Data from WHOOP's medical features (WHOOP MG). A summary of WHOOP's pages said this is not in the API. We could not open the exact page, so confirm with WHOOP.
- Write access. The API reference lists read endpoints plus one call to revoke access, and nothing that writes data back.
- A published history window. Test how far back your first pull goes.
How to get access
- Sign in to the Developer Dashboard at developer-dashboard.whoop.com with a WHOOP account. Whether you need a paid membership for this is not published. Same day.
- Create a Team, then an app (up to 5 apps per team). Add at least one redirect URI and one scope. You get a Client ID and Client Secret. Same day.
- Build on the Sandbox tier. Up to 10 WHOOP members can connect. No approval needed.
- Prepare for review. WHOOP's prerequisites: follow the API Terms, test with at least one member, keep app info accurate, follow the Design and Brand Guidelines.
- Request the next tier in the dashboard. WHOOP reviews requests by hand, in order received, and answers by email. Vague requests are rejected. Wait time not published.
- Repeat for each tier. From the Build tier onward, at least 50% of the current tier's member limit must be connected before you can move up. WHOOP's member tiers: Sandbox 10, Build 100, Growth 1,000, Scale 5,000, Production unlimited.
- For any PHI use, ask WHOOP for written consent under terms 1.8. Timeline not published.
From zero to your first WHOOP data in four steps
- Register an app. In the Developer Dashboard, create a Team and an app, add a redirect URI and the scopes you need, and note the Client ID and Client Secret.
- Connect a member. Send them to https://api.prod.whoop.com/oauth/oauth2/auth with your scopes and offline, plus a state value of eight characters. Swap the code for tokens at https://api.prod.whoop.com/oauth/oauth2/token on your server.
- Pull recent sleep. Collections return at most 25 records per page, newest first, with a next_token for the next page.
curl 'https://api.prod.whoop.com/developer/v2/activity/sleep?start=2026-10-01T00:00:00.000Z&limit=25' \ --header 'Authorization: Bearer <access_token>' - Listen for changes. Add a webhook URL in the dashboard with the v2 model version. On sleep.updated, fetch /v2/activity/sleep/{id}. To test, edit a past sleep in the WHOOP app by one minute. WHOOP says that sends both sleep.updated and recovery.updated.
Terms you must know
From the WHOOP API Terms of Use, effective 6 Oct 2026.
- Medical device, 3.1(10). You may not use the API to "design, develop, augment, or support a medical device". Healthcare: an FDA-regulated RPM or diagnostic product cannot use WHOOP data in its device function. Wellness: a fitness or sleep app that makes no medical claims is outside this clause, but have counsel check your copy.
- Medical advice, 3.1(11). No using the API to give "medical, legal, or other professional advice". Healthcare: a clinician acting on WHOOP data inside your product is a gray area to clear with counsel and WHOOP. Wellness: keep coaching copy general and avoid diagnosis language.
- PHI, 1.8. No transmitting Protected Health Information without WHOOP's prior written consent. Healthcare: a covered entity or business associate storing WHOOP data against a patient record needs this consent first. Wellness: the clause still names PHI, so check it before you sell to health plans, employers' health programs or providers.
- BAA. Not published. Healthcare: ask WHOOP before you plan on one. Wellness: usually not relevant unless you serve a covered entity.
- Storage, 4.2(2). No databases or permanent copies of WHOOP Data beyond what cache headers allow. Healthcare: this conflicts with keeping readings in an EHR or trial database. Wellness: long-term trend screens built on stored history are also at risk. Raise it with WHOOP before you design storage.
- AI training, 4.2(3). No using WHOOP Data to train or improve any large language model or any other machine learning or artificial intelligence model. Both readers: keep WHOOP data out of fine-tuning sets and model feedback loops.
- Selling data, 3.1(3) and 4.2(4). No selling or licensing WHOOP data, even with user consent. Payers and data businesses cannot resell it.
- Branding. You must follow WHOOP's Design and Brand Guidelines. This is a tier-review prerequisite.
- Termination, 7.1. WHOOP may end the terms or discontinue the API at any time. Healthcare: have a fallback in your program protocol. Wellness: do not make WHOOP the only data source.
- FDA status of the strap. Not published in WHOOP's developer docs. Healthcare: do not describe WHOOP readings as from a cleared device unless WHOOP confirms it for your use.
- Data residency. Not published. Healthcare and non-US programs: ask where WHOOP stores data and whether you can choose a region.
- Competing products. No specific clause in our research. Read the full terms before building a recovery or strain score of your own.
Cost and payment terms
- Developer fee: none today (terms 9.1). WHOOP will give notice before charging.
- Rate limit increases: on request in the dashboard. No price published.
- End user: needs a WHOOP strap and account. Membership pricing is not in our sources.
- Healthcare Partner API: pricing not published.
- Aggregators: pricing not published.
Use cases
Employer wellness challenge
An employee taps "Connect WHOOP" in your app and approves the sleep, recovery and cycle scopes. WHOOP sends sleep.updated and recovery.updated webhooks. Your server fetches the record by ID and updates the employee's sleep and recovery screens and the team leaderboard. Data used: sleep performance, recovery score, cycle strain.
- Concurrent token refresh. Two workers refresh the same member, and one token chain breaks. Fix: one refresh per member at a time, with a lock.
- Tier cap. You hit the member limit on launch day. Fix: request the next tier early, and remember you need 50% of the current limit connected first.
- Storage clause. The challenge history lives in your database. Fix: clear long-term storage with WHOOP before launch.
Sports medicine clinic training load
An athlete connects WHOOP through the clinic portal. Workout and recovery webhooks fire after each sync. Your server pulls the workout, recovery and cycle records and shows a weekly load and recovery chart to the clinician. If the clinic wants the data in its EHR, you map heart rate and SpO2 to FHIR Observations. That step needs WHOOP's written PHI consent first.
- No beat-level data for return-to-play protocols. Fix: use workout zone time and average heart rate, or a device with raw access.
- Advice clause. The screen reads as clinical guidance. Fix: show trends, let the clinician decide, and confirm the setup with WHOOP.
Sleep coaching app
The user connects WHOOP. On each sleep.updated event, your server pulls the sleep record and gives the coach stage times, efficiency and consistency. The app shows a nightly card and a weekly summary.
- Deleted sleeps. A sleep.deleted event arrives for a record you already used. Fix: handle delete events and recompute the week.
- Missed webhooks. Your endpoint is down for longer than the retry window (5 retries over about an hour). Fix: a nightly pull of the last few days to catch gaps.
Research study with free-living participants
Participants consent in the study app and connect WHOOP. A daily job pulls recovery, sleep and cycle records for each participant and writes them to the study dataset. Coordinators see a compliance view of who synced.
- Sandbox cap. 10 participants only. Fix: plan tier requests into the study timeline.
- Retention. The study must keep data for years. Fix: get WHOOP's written agreement on storage before enrollment.
- Rate limit. The default is 10,000 requests a day for the app, whatever the number of participants. Fix: use webhooks, fetch by ID, and request an increase before enrollment grows.
RPM or chronic care program (diabetes, CGM, hypertension)
This is the go/no-go case for a clinical buyer. Terms 3.1(10) bar WHOOP data from any medical device function, and 3.1(11) bars medical advice, so WHOOP cannot be the reading your program bills or alerts on. What can work: the patient connects WHOOP in your patient app as an optional extra, a daily job pulls sleep, recovery and strain, and your app shows them next to the readings from your cleared device as lifestyle context. Before any of it reaches the care team or the EHR, you need WHOOP's written PHI consent under 1.8.
- Scope creep. A care manager starts acting on recovery or HRV changes. Fix: keep WHOOP data out of alert rules and protocols, and confirm the setup with WHOOP and counsel.
- Storage. Your program keeps records for years, which conflicts with 4.2(2). Fix: get WHOOP's written agreement on storage before go-live, or show WHOOP data live and do not store it.
- No raw data. CGM and RPM teams often want time series. WHOOP gives daily summaries only. Fix: pick a device with a raw data route for anything the program depends on.
Payer or health plan wellness incentive
A member links WHOOP in the plan's app. A monthly job reads cycle steps and sleep consistency to check a reward goal. The result goes to the rewards system, not to claims.
- PHI. Data a health plan holds about its members is likely PHI. Fix: get WHOOP's written consent under 1.8 before launch.
- Data resale. Sharing derived data with partners can breach 4.2(4). Fix: keep WHOOP data inside the reward check.
WHOOP data in an EHR or remote monitoring program
Most healthcare teams want WHOOP readings next to clinical data, not in a separate app. The usual pattern is to turn each value into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Clear the PHI clause (1.8) and the storage clause (4.2(2)) with WHOOP first, because they decide whether you may do this at all.
| WHOOP value | FHIR Observation | Code |
|---|---|---|
| resting_heart_rate (recovery) | Heart rate, beats per minute | LOINC 8867-4 |
| spo2_percentage (recovery) | Oxygen saturation, percent | LOINC 2708-6, plus 59408-5 for pulse oximetry |
| respiratory_rate (sleep) | Respiratory rate | LOINC 9279-1 |
| skin_temp_celsius (recovery) | Skin temperature, degrees Celsius | LOINC 39106-0 |
| weight_kilogram, height_meter (body) | Body weight, body height | LOINC 29463-7, 8302-2 |
| Light plus slow wave plus REM time (sleep) | Sleep duration | LOINC 93832-4 |
| HRV (RMSSD), recovery score, strain | Device-specific Observation | Your own code system. The common HRV code, 80404-7, is SDNN, a different measure. Recovery and strain are WHOOP's own scores. |
Keep the WHOOP record id on each Observation. A webhook update or delete then finds it again, and a recovery.deleted event carries the id of the linked sleep, not the cycle.
Known blockers and gotchas
- Rotating refresh tokens. Each refresh invalidates the old access token and returns a new refresh token. Concurrent refreshes fail. Serialize refresh per member.
- No offline scope, no refresh token. Forget "offline" and the member must sign in again when the token expires (sample shows 3,600 seconds). Always request it.
- v1 is gone. WHOOP says v1 webhooks have been removed. IDs changed to UUIDs in v2. Use the migration guide and GET /v1/activity-mapping/{activityV1Id} to map old IDs.
- Daily rate limit. 10,000 requests a day by default. A naive poller across a few hundred members hits it fast. Request an increase and lean on webhooks.
- Tier gate needs real usage. You cannot jump tiers on a forecast. Time pilots so that half of each tier is connected before you ask.
- Webhooks carry IDs only. The payload has user_id, id, type and trace_id. Every event costs at least one API call, which counts against your rate limit. Verify the HMAC-SHA256 signature before you fetch anything.
- Updates replace earlier values. WHOOP sends updated events when a sleep, recovery or workout record changes. Upsert by record ID and never append duplicates.
- Disconnects. When a member leaves your program, call DELETE /v2/user/access so the grant is revoked on WHOOP's side, then delete or keep data according to the terms.
- Terms change. The current terms took effect 6 Oct 2026. Recheck them before each contract renewal.
Delivery timeline
Our estimate for a first integration. Steps marked "vendor" depend on WHOOP.
| Week | Work | Depends on vendor? |
|---|---|---|
| 1 | Register app, OAuth with offline scope and refresh lock, Sandbox with test members | No |
| 2 | Endpoints for cycle, recovery, sleep, workout, body. Webhook receiver with signature check. | No |
| 3 | Storage design within terms, FHIR mapping if needed, gap-fill job, delete handling | No |
| 3 to 4 | Brand review, first tier request | Vendor |
| Before clinical use | Written PHI consent and storage agreement | Vendor, no published timeline |
Questions to ask WHOOP before you sign
- Will you give written consent under terms 1.8 for our PHI use, and on what conditions?
- Will you sign a BAA?
- Can we keep WHOOP data in an EHR or study database for our retention period, given 4.2(2)?
- How long does a tier review take? The member limits per tier are published, the wait is not.
- Does a member with a lapsed membership still return data through the API?
- How far back does the API return history for a newly connected member?
- Is WHOOP MG medical feature data available through any API?
- Is the Healthcare Partner API open to us, and what does it cost?
Other device integration guides
WHOOP 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
- 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
- Polar API integration guide
- COROS API integration guide
- Suunto API integration guide
- Strava API integration guide
- Peloton API integration guide
- MyFitnessPal API integration guide
Ready to build with WHOOP?
We build device integrations into healthcare and wellness products, including FHIR mapping and EHR delivery. We have no partnership with WHOOP. 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. Book a call about your device integration.
For whoever builds this
- OAuth 2.0 authorization code. Auth: https://api.prod.whoop.com/oauth/oauth2/auth. Token: https://api.prod.whoop.com/oauth/oauth2/token.
- Scopes: read:recovery, read:cycles, read:workout, read:sleep, read:profile, read:body_measurement, offline.
- Access token lifetime comes from expires_in (sample 3600). Refresh tokens rotate. Using one invalidates the old access token.
- Endpoints: GET /v2/cycle, /v2/cycle/{id}, /v2/recovery, /v2/cycle/{id}/recovery, /v2/activity/sleep, /v2/activity/workout, /v2/user/measurement/body, /v2/user/profile/basic, DELETE /v2/user/access.
- Rate limits: 100 per minute, 10,000 per day by default. HTTP 429 on excess. Increase on request.
- Webhooks: workout.updated, workout.deleted, sleep.updated, sleep.deleted, recovery.updated, recovery.deleted. Payload: user_id, id (UUID), type, trace_id. HMAC-SHA256 signature using the client secret. 5 retries over about an hour. Payload carries no data, so fetch by id.
- v1 to v2: v1 webhooks removed. GET /v1/activity-mapping/{activityV1Id} maps old IDs. Exact v1 removal date not published.
- FHIR (LOINC from the FHIR R4 vital signs profile): heart rate 8867-4, SpO2 2708-6, respiratory rate 9279-1, body weight 29463-7, body height 8302-2.
- Skin temperature: 39106-0 Temperature of Skin (checked 11 Nov 2026). Do not use 8310-5, which is body temperature. Unverified: HRV RMSSD (80404-7 is SDNN, a different measure), sleep stages. Recovery and strain are WHOOP scores and need a local code system.
Sources
All read 10 Nov 2026.
- WHOOP Apple Health integration, https://support.whoop.com/s/article/Apple-Health-Integration?language=en_US, read 10 November 2026.
- WHOOP Health Connect integration, https://support.whoop.com/s/article/Google-Health-Integration-For-Android?language=en_US, 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.
- https://developer.whoop.com/docs/introduction
- https://developer.whoop.com/docs/developing/getting-started/
- https://developer.whoop.com/docs/developing/app-approval/
- https://developer.whoop.com/docs/developing/oauth
- https://developer.whoop.com/docs/developing/rate-limiting
- https://developer.whoop.com/docs/developing/webhooks/
- https://developer.whoop.com/docs/developing/v1-v2-migration
- https://developer.whoop.com/docs/developing/design-guidelines/
- https://developer.whoop.com/api
- https://developer.whoop.com/api-terms-of-use/
- https://developer.whoop.com/docs/partner/overview/
- https://whoop.com/thelocker/access-your-whoop-data-with-new-integrations-data-export-options
- https://hl7.org/fhir/R4/observation-vitalsigns.html
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does WHOOP have a public API?
How much does the WHOOP API cost?
Can I get heart rate time series from WHOOP?
Does WHOOP have a mobile SDK or an Apple Health route for developers?
Is the WHOOP API HIPAA compliant?
Can I use WHOOP data in a remote patient monitoring or medical device product?
How many users can connect to my WHOOP app?
What are the WHOOP API rate limits?
Which WHOOP webhooks are available?
Can I store WHOOP data in my database or EHR?
Can I train an AI model on WHOOP data?
Is WHOOP API v1 still available?
Which OAuth scopes does the WHOOP API use?
How much history do I get when a member first connects?
What are the WHOOP member tiers?
Does every webhook go to every URL?
How do I verify a WHOOP webhook signature?
What units does the WHOOP API use?


