Withings API Integration Guide 2026: RPM, Data, Pricing
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.

The Withings API lets you connect Withings scales, blood pressure monitors, sleep devices and watches to your product through the Withings cloud. The free plan lets you start the same day with 10 users. It has no business associate agreement (BAA), it is hosted in the EU, and users whose Withings accounts were created after 12 October 2026 need a paid Withings+ subscription. If you will handle US patient data, plan on the Enterprise contract from the start. That one choice decides most Withings projects.
Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery, and our remote patient monitoring software work covers RPM programs.
Withings integration at a glance
| Question | Short answer |
|---|---|
| Is there an official API? | Yes. A public cloud API with OAuth 2.0 and webhook notifications. |
| Cost to the developer | Free plan for up to 10 users. Enterprise and Advanced Biomarkers plans are custom priced. No dollar prices are published. |
| Does the end user need to pay? | On the free plan, yes for accounts created after 12 October 2026 (Withings+). Withings can remove this for Cellular, SDK and Research partners on Enterprise. |
| Same-day start? | Yes. Create an app on the developer portal and test with the demo user. |
| Who approves scale-up? | Withings. More than 10 users needs an app review. Enterprise needs a sales contract. Waiting time is not published. |
| HIPAA and BAA | Enterprise only. The free plan has no HIPAA support and no BAA. |
| Raw or summary data? | Individual measurements for weight and blood pressure. Daily summaries for activity and sleep. ECG, AFib and SpO2 results need the Advanced Biomarkers plan. |
| First build | About 3 weeks for a working integration. This is our estimate. Contracts can add more. |
Integration strategies
| Route | Own mobile app? | Own server? | Vendor approval or contract? | SDK? | Latency | Supported data | Not supported | Best for |
|---|---|---|---|---|---|---|---|---|
| Public cloud API (free plan) | No | Yes | No for 10 users. App review above that. | No | Not published. Poll at most every 10 minutes per user. | Weight, body composition, blood pressure, heart rate, temperature, activity, sleep summary, device list | BAA, US hosting, cleared biomarkers | Prototypes and wellness apps |
| Webhooks (notify) | No | Yes, a public HTTPS endpoint | Same as the API plan you use | No | Push on new data. Typical delay is under 2 minutes, with no real-time SLA on the standard plan. | Alerts for body, sleep, blood pressure, activity. ECG alerts, which carry the AFib result, only matter on Advanced Biomarkers. | The data itself. You fetch it after the alert. | Every production build |
| Enterprise plan | No | Yes | Yes, sales contract | No | Same API | Same as free, unlimited users, higher rate limit | Cleared biomarkers (need Advanced Biomarkers) | US healthcare with patient data |
| Advanced Biomarkers plan | No | Yes | Yes, contract | No | Same API | Adds ECG, AFib, SpO2, vascular age, AHI, EDA/NHS, risk scores | Not published | Cardiac and sleep programs, research |
| Cellular devices and dropship | No. The patient needs no phone. | Yes | Yes, contract | No | Device sends over cellular to the Withings cloud, then to you | Readings from BPM Connect Pro, Body Pro, BPM Pro 2 | Other device models. Coverage areas not published. | Remote patient monitoring (RPM) for patients without a smartphone |
| Apple Health | Yes | Optional | No | HealthKit | Sync is manual on iPhone. Open both apps. | The categories the user picks, such as weight, body fat, blood pressure, heart rate, sleep, steps and workouts | Android users. Accounts made after 13 October 2026 need Withings+ to export. | iPhone apps that already read HealthKit |
| Aggregators, checked 10 November 2026 | Terra, Junction, Thryve and ROOK list Withings as a cloud API source. Spike lists it with no route stated. Validic lists only Withings Pro cellular devices, weight, blood pressure and pulse, and they need Withings approval. Sahha coverage is not published. Pricing is not published. | |||||||
| Phone SDK | Yes | Not published | Yes. Withings names SDK partners on Enterprise. | Yes | Not published | Not published | Not published | Ask Withings sales. We did not review SDK docs. |
| Android Health Connect | Yes | Optional | No | Health Connect | After phone sync | The categories the user picks | Accounts made after 13 October 2026 need Withings+ to export | Android apps already on Health Connect |
| File export | No | No | No | No | Manual | Not published | Not published | Not covered in our sources |
| Withings RPM platform | No | No | Yes | No | Not published | Provider-facing dashboard | Your own product screens | Clinics that want a ready dashboard, not an integration |
Healthcare buyers should go straight to Enterprise with webhooks, and add the Cellular program if patients are older or lack smartphones. Wellness teams can start on the free plan and webhooks, but should check how many new users will hit the Withings+ requirement before launch.
Build it yourself, use an aggregator, or work with a partner
| Question | Build in-house | Wearable aggregator | Build with a partner (Nirmitee) |
|---|---|---|---|
| Whose Withings API app? | Yours | Depends on the aggregator. Not published on the pages we read. | Yours. We build it in your account. |
| BAA and US hosting | Your Enterprise contract with Withings | Ask the aggregator whether its Withings setup includes a BAA and US hosting. Not published. | Your Enterprise contract. We design the pipeline around it. |
| Cellular RPM devices | Your Cellular contract and the logistics API | Validic lists Withings Pro cellular devices, with Withings approval. Others do not say. | Your Cellular contract. We build the order and device linking calls. |
| 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 | Withings measure types and 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 weeks of build in our estimate, plus any Withings contract time |
| Cost shape | Engineering time | Aggregator fee. Pricing is not published. | Project fee, scoped after a call |
What data you can get
| Data type | Granularity | History window | Push or pull |
|---|---|---|---|
| Weight, fat ratio, fat mass | Each measurement | Not published | Webhook alert, then pull with getmeas |
| Blood pressure (systolic, diastolic) and heart rate | Each measurement | Not published | Webhook alert, then pull |
| Body, skin and general temperature | Each measurement | Not published | Webhook alert (temperature), then pull with getmeas |
| SpO2 | Each measurement, Advanced Biomarkers plan | Not published | Webhook alert (blood pressure category), then pull |
| Activity (steps and related totals) | Daily summary | Not published | Webhook alert, then pull with getactivity |
| Sleep | Nightly summary | Not published | Webhook alert, then pull with getsummary |
| ECG and AFib | Per recording, Advanced Biomarkers plan | Not published | Webhook alert, then pull |
| Devices | List per user | Current | Pull with getdevice |
Device families covered by the API include connected scales, blood pressure monitors, sleep mats, watches, thermometers, BeamO and U-Scan. Withings lists 96 biomarkers across 9 device families. The OpenAPI file at developer.withings.com is the full list of endpoints. Intraday activity, workouts and the full ECG signal have their own endpoints: getintradayactivity, getworkouts and Heart v2 get.
What is inside one Withings night of sleep data
The sleep summary gives totals. The high-frequency sleep call (Sleep v2 get) gives the night itself. These fields come from the Withings OpenAPI spec.
| Field | What it holds |
|---|---|
| state | Sleep stage per segment, with a start and end time: 0 awake, 1 light, 2 deep, 3 REM, 4 manual, 5 unspecified. Value 15, out of bed, needs a specific plan. |
| hr and rr | Heart rate in beats per minute and respiration rate in breaths per minute, as series keyed by timestamp. The sample interval is not published. |
| sdnn_1, rmssd, hrv_quality | Heart rate variability: SDNN over 1 minute and RMSSD, both in milliseconds, plus a quality score |
| snoring, breathing_sounds | Snoring time and time with breathing sounds, in seconds |
| mvt_score, chest_movement_rate | Movement in bed, and chest movement events per minute |
| withings_index | Breathing events per hour: 0 to 15 none or mild, 15 to 30 moderate, above 30 severe. It needs 5 hours of sleep. |
| model | 16 for a tracker, 32 for a sleep monitor, plus the device model name |
Some of these values are regulated in the EU and US, so Withings says they may not be available in your region. For scales and cuffs, getmeas returns measure groups. Each group has a grpid, a date and a list of measures, and each measure has a value, a type and a unit. The real value is value x 10^unit, so 7500 with unit -2 is 75.00 kg.
What you cannot get
- ECG, AFib, SpO2, vascular age, AHI (sleep apnea index) and EDA results on the free or Enterprise plans. They need Advanced Biomarkers.
- A BAA, HIPAA support or US hosting on the free plan.
- Data from users with new accounts on the free plan unless they pay for Withings+.
- A published history window. Webhook delay is typically under 2 minutes, but Withings does not commit to it on the standard plan.
- Every device in every country. Sleep Analyzer is sold in the EU, Australia and the UK. Sleep and Sleep Rx are the US versions.
How to get access
- Create a developer app on developer.withings.com. This is self-serve.
- Test sign-in and data calls with the demo user (add mode=demo to the sign-in link).
- Connect up to 10 real users on the free plan.
- To go past 10 users, ask Withings for an app review. Withings approves it. Waiting time is not published.
- For Enterprise, Advanced Biomarkers or Cellular, fill in the API plans form to reach Withings sales. Expect a security questionnaire, a data processing agreement and a BAA. Timing is not published.
- For cellular RPM kits, agree the logistics setup so Withings can ship devices to patients.
From zero to your first Withings data in four steps
- Create an app. Register it in the Withings developer dashboard at developer.withings.com/dashboard and note the client ID and client secret.
- Sign in as the demo user. Send the browser to account.withings.com/oauth2_user/authorize2 with your scopes and &mode=demo, so you need no device. Swap the code for tokens at wbsapi.withings.net/v2/oauth2 with action=requesttoken within 30 seconds.
- Pull your first measures. Every call is a POST with form fields and a Bearer token. This one asks for weight, blood pressure and heart rate.
Check that the body status is 0. If the body has more=1, call again with the offset it gives.curl --header "Authorization: Bearer YOUR_ACCESS_TOKEN" \ --data "action=getmeas&meastypes=1,9,10,11&startdate=1728000000&enddate=1728171131" \ 'https://wbsapi.withings.net/measure' - Subscribe to webhooks. Call notify with action=subscribe, your callback URL and one appli value, for each user and each category. The URL must be HTTPS on a real domain, on port 80 or 443, at most 255 characters, and it must answer a HEAD request with a 2xx. If it does not, the app stays in restricted mode with at most 10 linked users.
Terms you must know
We read the plans page and the developer docs. We did not read the full Withings API terms of use, so we cannot quote section numbers. Ask for the current terms before you sign.
- PHI and HIPAA. The free plan offers no HIPAA support. The Withings HIPAA guide says API use can make Withings a business associate. For a healthcare product, that means no patient data until Enterprise and a signed BAA. A wellness product without covered-entity clients can use the free plan, within its 10-user cap and EU hosting.
- BAA. Enterprise only. A clinic or payer client will ask you for it in procurement.
- Storage and hosting. Free plan data is hosted in the EU. Enterprise offers US hosting. If your clients require US hosting, the free plan cannot meet that.
- AI training and anonymization. These appear as features of the Advanced Biomarkers plan. The rules for training your own models on free or Enterprise data are not published on the pages we read. Ask in writing.
- End-user subscription. Withings+ is required on the free plan for accounts created after 12 October 2026. A wellness app aimed at new Withings buyers should expect many of them to hit this. How the API responds for a user without Withings+ is not published, so test it with a fresh account. Enterprise can drop this for Cellular, SDK and Research partners.
- Medical use. Withings states BPM Pro 2 is CE marked and FDA cleared. ECG, AFib, SpO2 and similar results come as FDA or CE cleared biomarkers under Advanced Biomarkers. What the API terms say about medical use of the data is not published on the pages we read.
- Display and branding, data selling, termination and competing products. Not covered in our sources. Ask Withings.
Cost and payment terms
- Free plan: no fee, 10 users, standard rate limit.
- Enterprise: custom price based on active users. Unlimited users, more than 1,500 requests per minute, HIPAA, BAA, US hosting.
- Advanced Biomarkers: custom price based on users and biomarkers.
- Withings+ for end users: required on the free plan for new accounts. The price is not in the Withings developer docs.
- Devices: you or the patient buy the hardware. Device prices are outside our sources.
- Aggregator fees: not published in our sources.
Use cases
Hypertension remote monitoring
The clinic ships a cellular BPM Connect Pro or BPM Pro 2 to the patient through Withings dropship. The patient takes a reading. The cuff sends it over cellular to the Withings cloud. Withings calls your webhook with the blood pressure code. Your server pulls the reading with getmeas, stores systolic, diastolic and heart rate, and writes FHIR Observations to the EHR. Data used: blood pressure and heart rate.
- Webhook missed during an outage. Run a daily catch-up pull per patient, at most once every 10 minutes.
- Device not linked to the right patient. Record the device serial at shipping and check it against getdevice.
- Values look wrong by a factor of ten. Apply value x 10^unit before storing.
Heart failure weight watch
The patient steps on a cellular Body Pro scale each morning. A webhook fires for body data. You pull weight, compare with the last days, and flag a quick gain to the care team. Data used: weight.
- Someone else uses the patient's scale. How Withings assigns readings on a shared cellular scale is not published. Let the care team reject a reading that looks wrong.
- Reading late or missing. Alert on no reading by a set time, not only on high values.
Clinical trial with sleep and cardiac endpoints
Participants use a watch and a sleep device. Under Advanced Biomarkers, webhooks fire for sleep and ECG, and the AFib result comes with each ECG record. You pull the data into the trial database. Data used: sleep summary, ECG, AFib, SpO2. SpO2 arrives under the blood pressure notification category, so pull it with getmeas after that alert.
- Plan signed without Advanced Biomarkers. Confirm the plan covers every endpoint before the protocol is final.
- Refresh token expired after a year. Track token age and ask the participant to sign in again before it lapses.
Weight loss and nutrition coaching app
A user connects Withings in your app through OAuth. When a new weigh-in arrives you show the trend and the coach sees it. Data used: weight, fat mass, activity.
- New user blocked by Withings+. Tell users before they connect, or move to Enterprise.
- Stuck at 10 users. Request the app review early.
Employer wellness challenge
Staff connect Withings for steps and sleep. A daily activity webhook updates the leaderboard. Data used: daily activity and sleep summary.
- Rate limit status 601 inside an HTTP 200. Read the body status, back off and retry.
Withings data in an EHR or remote monitoring program
Most healthcare teams want Withings 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. Sign the Enterprise contract and BAA before any patient data flows.
| Withings value | FHIR Observation | Code |
|---|---|---|
| Weight (measure type 1) | Body weight, kg | LOINC 29463-7 |
| Systolic and diastolic (types 10 and 9) | Blood pressure panel with two components, mmHg | LOINC 85354-9, with 8480-6 and 8462-4 |
| Heart rate (type 11) | Heart rate, beats per minute | LOINC 8867-4 |
| SpO2 (type 54) | Oxygen saturation by pulse oximetry, percent | LOINC 59408-5, plus 2708-6 |
| Body temperature (types 12 and 71) | Body temperature, Celsius | LOINC 8310-5 |
| Fat ratio (type 6) | Percentage of body fat | LOINC 41982-0 |
| Steps (getactivity) | Number of steps | LOINC 55423-8 |
| Respiration rate during sleep (rr) | Respiratory rate, breaths per minute | LOINC 9279-1 |
| ECG result, AFib, vascular age, Withings index, sleep score | Device-specific Observation | Your own code system. These are Withings results, so no standard code fits exactly. |
Apply value x 10^unit before you write the Observation. Keep the Withings grpid on it, so a later update or delete can find it again. The user profile change notification (appli 46) tells you when a user deletes the account or unlinks your app.
Known blockers and gotchas
- HTTP 200 does not mean success. Withings returns status 601 in the body when you are rate limited. Check the body status on every call.
- Polling too often. Do not poll a user more than once every 10 minutes. Use webhooks and pull after the alert.
- Refresh token rotation. The old refresh token dies 8 hours after a new one is issued, or once the new access token is used. Save the new token before you use it, in one transaction.
- 30-second auth code. Exchange the code at once in the callback. A queue delay will break sign-in.
- Withings+ paywall. From 12 October 2026 new free-plan users need Withings+. Test with a new account, not an old one.
- Cleared biomarkers are a separate plan. ECG, AFib and SpO2 are not in Enterprise by default.
- Deprecated token endpoints. A Withings support article lists older token endpoints as deprecated. Use /v2/oauth2.
- Signed partner calls. Some partner endpoints need HMAC-SHA256 signatures with a nonce. Build this early if you use dropship.
Delivery timeline
Our estimate for a first integration.
| Week | Work | Depends on Withings? |
|---|---|---|
| 1 | Developer app, OAuth with the demo user, getmeas, webhook endpoint | No |
| 2 | Token rotation, 601 handling, catch-up pull, device list | No |
| 3 | FHIR mapping, EHR or app screens, testing with real users | No |
| In parallel | Enterprise contract, BAA, US hosting | Yes |
| In parallel | Cellular contract and dropship logistics for RPM kits | Yes |
| After review | More than 10 users on the free plan | Yes |
Questions to ask Withings before you sign
- How long do app review and the Enterprise contract usually take?
- Will you sign a BAA, and is US hosting included in the base Enterprise price?
- Which biomarkers come with Enterprise, and which need Advanced Biomarkers?
- Can you remove the Withings+ requirement for our users, and on what terms?
- How much history can we pull when a user first connects?
- What do the terms say about medical use, AI training, data resale and termination?
- What is the exact rate limit on our plan?
- How does dropship work for patient returns and device swaps?
Other device integration guides
Withings 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.
- Apple Health API Integration Guide
- COROS API Integration Guide
- Dexcom API Integration Guide
- Eight Sleep API
- Fitbit API
- FreeStyle Libre API
- Garmin API Integration Guide
- Health Connect API Integration Guide
- MyFitnessPal API
- Oura Ring API Integration Guide
- Peloton API
- Polar API Integration Guide
- Samsung Health API Integration Guide
- Strava API Integration Guide
- Suunto API Integration Guide
- Ultrahuman API Integration Guide
- WHOOP API Integration Guide
Book a call about your device integration
We do not have a partnership with Withings. 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. Authorize at https://account.withings.com/oauth2_user/authorize2. Token at https://wbsapi.withings.net/v2/oauth2.
- Scopes: user.info, user.metrics, user.activity, user.sleepevents.
- Token life: auth code 30 seconds, access token 3 hours, refresh token 1 year. Old refresh token dies 8 hours after a new one is issued or once the new access token is used.
- Demo user: add &mode=demo to the authorize URL.
- Measures: POST https://wbsapi.withings.net/measure action=getmeas. Types 1 weight kg, 6 fat ratio, 8 fat mass, 9 diastolic, 10 systolic, 11 heart rate, 12 temperature, 54 SpO2, 71 body temperature, 73 skin temperature. Real value = value x 10^unit.
- Other calls: /v2/measure action=getactivity, /v2/sleep action=getsummary, /v2/user action=getdevice.
- Webhooks: notify subscribe and list. Appli codes 1 weight and body composition, 2 temperature, 4 blood pressure, heart rate and SpO2, 16 activity, 44 sleep, 54 ECG, 58 glucose, 46 user profile change. There is no separate AFib category: the AFib result comes with the ECG record.
- Rate limits: poll at most every 10 minutes per user. Body status 601 means rate limited. Enterprise is above 1,500 requests per minute. The standard limit is 120 requests per minute across your application, per the Withings notifications overview page.
- Signing: some partner endpoints need HMAC-SHA256 with a nonce.
- Full endpoint list: https://developer.withings.com/openapi.yaml.
- FHIR and LOINC (each code checked against the NLM LOINC search on 11 November 2026): weight 29463-7, systolic 8480-6, diastolic 8462-4, BP panel 85354-9, heart rate 8867-4, SpO2 59408-5, body temperature 8310-5, steps 55423-8.
- Version notes: older token endpoints deprecated. Withings+ rule for free-plan users from 12 October 2026.
Sources
All read on 10 November 2026.
- Withings export to partner apps, https://support.withings.com/hc/en-us/articles/51884267429265-Partners-Exporting-from-the-Withings-App-to-Partner-Apps, read 10 November 2026.
- Withings API terms of use, version dated 12 September 2018, https://media.withings.com/web/legal/legal-pdf/api-terms-of-use/wo-en-api-terms-of-use-20180912.pdf, 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.
- Withings API reference
- Withings: all available health data
- Withings API plans
- Withings developer docs (llms.md)
- Withings access and refresh tokens
- Withings BPM Pro 2 (search listing)
- Validic: Withings Pro Cellular integration (search listing)
- Withings API plans form
- Withings HIPAA compliance guide (search excerpt)
- Withings: deprecating token endpoints (search listing)
Ready to scale?
Talk to our healthcare engineering team about building, integrating, and shipping faster.
Frequently Asked Questions
Does Withings have a public API?
Is the Withings API free?
Will Withings sign a BAA?
Do users need Withings+ for third-party apps?
Can I get ECG and AFib data from Withings?
Can Withings devices be used for remote patient monitoring without a smartphone?
Can I get Withings data through Apple Health instead of the API?
How do I get real-time Withings data?
How long do Withings OAuth tokens last?
What is Withings error 601?
How long does a Withings integration take?
Which Withings notification categories should I subscribe to?
What happens if my Withings webhook endpoint is down?
What is the Withings API rate limit?
How do I load a user's history and keep it in sync?
Can I get the full ECG waveform from Withings?
Why does my Withings app stay limited to 10 users?


