Device IntegrationHealthcare Interoperability

Withings API Integration Guide 2026: RPM, Data, Pricing

July 7, 202616 min read
Written by
Jitendra Choudhary
Jitendra Choudhary

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.

Withings API Integration Guide 2026: RPM, Data, Pricing

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

QuestionShort answer
Is there an official API?Yes. A public cloud API with OAuth 2.0 and webhook notifications.
Cost to the developerFree 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 BAAEnterprise 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 buildAbout 3 weeks for a working integration. This is our estimate. Contracts can add more.

Integration strategies

RouteOwn mobile app?Own server?Vendor approval or contract?SDK?LatencySupported dataNot supportedBest for
Public cloud API (free plan)NoYesNo for 10 users. App review above that.NoNot published. Poll at most every 10 minutes per user.Weight, body composition, blood pressure, heart rate, temperature, activity, sleep summary, device listBAA, US hosting, cleared biomarkersPrototypes and wellness apps
Webhooks (notify)NoYes, a public HTTPS endpointSame as the API plan you useNoPush 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 planNoYesYes, sales contractNoSame APISame as free, unlimited users, higher rate limitCleared biomarkers (need Advanced Biomarkers)US healthcare with patient data
Advanced Biomarkers planNoYesYes, contractNoSame APIAdds ECG, AFib, SpO2, vascular age, AHI, EDA/NHS, risk scoresNot publishedCardiac and sleep programs, research
Cellular devices and dropshipNo. The patient needs no phone.YesYes, contractNoDevice sends over cellular to the Withings cloud, then to youReadings from BPM Connect Pro, Body Pro, BPM Pro 2Other device models. Coverage areas not published.Remote patient monitoring (RPM) for patients without a smartphone
Apple HealthYesOptionalNoHealthKitSync is manual on iPhone. Open both apps.The categories the user picks, such as weight, body fat, blood pressure, heart rate, sleep, steps and workoutsAndroid users. Accounts made after 13 October 2026 need Withings+ to export.iPhone apps that already read HealthKit
Aggregators, checked 10 November 2026Terra, 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 SDKYesNot publishedYes. Withings names SDK partners on Enterprise.YesNot publishedNot publishedNot publishedAsk Withings sales. We did not review SDK docs.
Android Health ConnectYesOptionalNoHealth ConnectAfter phone syncThe categories the user picksAccounts made after 13 October 2026 need Withings+ to exportAndroid apps already on Health Connect
File exportNoNoNoNoManualNot publishedNot publishedNot covered in our sources
Withings RPM platformNoNoYesNoNot publishedProvider-facing dashboardYour own product screensClinics 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

QuestionBuild in-houseWearable aggregatorBuild with a partner (Nirmitee)
Whose Withings API app?YoursDepends on the aggregator. Not published on the pages we read.Yours. We build it in your account.
BAA and US hostingYour Enterprise contract with WithingsAsk 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 devicesYour Cellular contract and the logistics APIValidic 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 renewalYou build and run themThe aggregator runs themWe build them, then hand them to you or run them
Data modelWithings measure types and fieldsThe aggregator's schemaFHIR Observations for your EHR or remote monitoring stack
Other devices laterOne new build per deviceMany devices through one APISame pattern reused across devices
Time to first real userDepends on your teamDepends on the aggregator's onboardingAbout 3 weeks of build in our estimate, plus any Withings contract time
Cost shapeEngineering timeAggregator fee. Pricing is not published.Project fee, scoped after a call
Every way to get Withings data, and what each one needs.

What data you can get

Data typeGranularityHistory windowPush or pull
Weight, fat ratio, fat massEach measurementNot publishedWebhook alert, then pull with getmeas
Blood pressure (systolic, diastolic) and heart rateEach measurementNot publishedWebhook alert, then pull
Body, skin and general temperatureEach measurementNot publishedWebhook alert (temperature), then pull with getmeas
SpO2Each measurement, Advanced Biomarkers planNot publishedWebhook alert (blood pressure category), then pull
Activity (steps and related totals)Daily summaryNot publishedWebhook alert, then pull with getactivity
SleepNightly summaryNot publishedWebhook alert, then pull with getsummary
ECG and AFibPer recording, Advanced Biomarkers planNot publishedWebhook alert, then pull
DevicesList per userCurrentPull 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.

FieldWhat it holds
stateSleep 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 rrHeart 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_qualityHeart rate variability: SDNN over 1 minute and RMSSD, both in milliseconds, plus a quality score
snoring, breathing_soundsSnoring time and time with breathing sounds, in seconds
mvt_score, chest_movement_rateMovement in bed, and chest movement events per minute
withings_indexBreathing events per hour: 0 to 15 none or mild, 15 to 30 moderate, above 30 severe. It needs 5 hours of sleep.
model16 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

  1. Create a developer app on developer.withings.com. This is self-serve.
  2. Test sign-in and data calls with the demo user (add mode=demo to the sign-in link).
  3. Connect up to 10 real users on the free plan.
  4. To go past 10 users, ask Withings for an app review. Withings approves it. Waiting time is not published.
  5. 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.
  6. 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

  1. Create an app. Register it in the Withings developer dashboard at developer.withings.com/dashboard and note the client ID and client secret.
  2. 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.
  3. 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.
    curl --header "Authorization: Bearer YOUR_ACCESS_TOKEN" \
      --data "action=getmeas&meastypes=1,9,10,11&startdate=1728000000&enddate=1728171131" \
      'https://wbsapi.withings.net/measure'
    Check that the body status is 0. If the body has more=1, call again with the offset it gives.
  4. 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

One blood pressure reading from the patient's cuff to the EHR.

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 valueFHIR ObservationCode
Weight (measure type 1)Body weight, kgLOINC 29463-7
Systolic and diastolic (types 10 and 9)Blood pressure panel with two components, mmHgLOINC 85354-9, with 8480-6 and 8462-4
Heart rate (type 11)Heart rate, beats per minuteLOINC 8867-4
SpO2 (type 54)Oxygen saturation by pulse oximetry, percentLOINC 59408-5, plus 2708-6
Body temperature (types 12 and 71)Body temperature, CelsiusLOINC 8310-5
Fat ratio (type 6)Percentage of body fatLOINC 41982-0
Steps (getactivity)Number of stepsLOINC 55423-8
Respiration rate during sleep (rr)Respiratory rate, breaths per minuteLOINC 9279-1
ECG result, AFib, vascular age, Withings index, sleep scoreDevice-specific ObservationYour 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.

WeekWorkDepends on Withings?
1Developer app, OAuth with the demo user, getmeas, webhook endpointNo
2Token rotation, 601 handling, catch-up pull, device listNo
3FHIR mapping, EHR or app screens, testing with real usersNo
In parallelEnterprise contract, BAA, US hostingYes
In parallelCellular contract and dropship logistics for RPM kitsYes
After reviewMore than 10 users on the free planYes

Questions to ask Withings before you sign

  1. How long do app review and the Enterprise contract usually take?
  2. Will you sign a BAA, and is US hosting included in the base Enterprise price?
  3. Which biomarkers come with Enterprise, and which need Advanced Biomarkers?
  4. Can you remove the Withings+ requirement for our users, and on what terms?
  5. How much history can we pull when a user first connects?
  6. What do the terms say about medical use, AI training, data resale and termination?
  7. What is the exact rate limit on our plan?
  8. 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.

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.

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does Withings have a public API?

Yes. Withings offers a cloud API with OAuth 2.0 sign-in and webhook notifications. You can create a developer app yourself and test with a demo user the same day.

Is the Withings API free?

The Start for Free plan costs nothing and covers up to 10 users. More users need a Withings app review. Enterprise and Advanced Biomarkers plans are custom priced, and Withings does not publish dollar prices.

Will Withings sign a BAA?

Only on the Enterprise plan, which also adds HIPAA support and US hosting. The free plan has no BAA and is hosted in the EU. Withings' own HIPAA guide says API use can make Withings a business associate.

Do users need Withings+ for third-party apps?

On the free plan, users whose accounts were created after 12 October 2026 need Withings+. Withings says it can remove this for Cellular, SDK and Research partners on Enterprise.

Can I get ECG and AFib data from Withings?

Yes, but only on the Advanced Biomarkers plan. That plan adds FDA or CE cleared biomarkers such as ECG, AFib, SpO2, vascular age and AHI. They are not part of the free or Enterprise plans.

Can Withings devices be used for remote patient monitoring without a smartphone?

Yes. Withings sells cellular devices such as BPM Connect Pro, Body Pro and BPM Pro 2 that send readings over a SIM to the Withings cloud. This needs a contract, and Withings can ship the devices to patients.

Can I get Withings data through Apple Health instead of the API?

Yes, if your app runs on iPhone and reads HealthKit, you get what the Withings app writes to Apple Health. Reports say new Withings accounts need Withings+ for Apple Health sync, but we did not confirm this on a Withings page. Android users are not covered by this route.

How do I get real-time Withings data?

Subscribe to webhook notifications for body, temperature, blood pressure and heart rate and SpO2, activity, sleep, ECG and glucose. The AFib result comes inside each ECG record. When a notification arrives, pull the new data. Do not poll a user more than once every 10 minutes.

How long do Withings OAuth tokens last?

The auth code lasts 30 seconds, the access token 3 hours and the refresh token 1 year. The old refresh token stops working 8 hours after a new one is issued or once the new access token is used.

What is Withings error 601?

Status 601 in the response body means you are rate limited. The HTTP status can still be 200, so always check the body status and back off.

How long does a Withings integration take?

Our estimate is about 3 weeks for a working integration. Enterprise contracts, BAAs and cellular logistics depend on Withings and can take longer. Withings does not publish waiting times.

Which Withings notification categories should I subscribe to?

Pick by data type: 1 weight and body composition, 2 temperature, 4 blood pressure, heart rate and SpO2, 16 activity, 44 sleep, 54 ECG and 58 glucose. Add 46 to hear when a user deletes the account or unlinks your app. You subscribe once per user for each category.

What happens if my Withings webhook endpoint is down?

Withings retries each notification in 5 cycles over about 5 hours, with 2 attempts per cycle. After 4 failed notifications in a row it sends warning emails, and after 20 days of failures it cancels the subscription. Missed notifications are not sent again, so backfill with the lastupdate parameter.

What is the Withings API rate limit?

The standard limit is 120 requests per minute across your whole application. Enterprise is above 1,500 per minute. Withings also asks you not to poll a user more than once every 10 minutes. A 601 status in the body means you hit the limit.

How do I load a user's history and keep it in sync?

Call getmeas with a startdate and enddate for the first load, and loop while the body says more=1, passing the offset it returns. After that, send lastupdate with the updatetime from your last response. Withings does not publish how far back the history goes, so test it on real accounts.

Can I get the full ECG waveform from Withings?

Yes, on the Advanced Biomarkers plan. Heart v2 list returns ECG records with the AFib classification. Heart v2 get returns the signal in microvolts with its sampling frequency in Hz.

Why does my Withings app stay limited to 10 users?

Either it has not passed the app review, or your callback URL does not meet the rules. The URL must be HTTPS on a real domain, on port 80 or 443, at most 255 characters, and answer a HEAD request with a 2xx. Otherwise the app stays in restricted mode with 10 linked users.
Share