Skip to content
AF
Alternatives

Withings API Alternatives: Aggregators and Health Stores (2026)

Last verified October 27, 2026 · 4 min read

Sources checked (16) · October 27, 2026
The main alternatives to integrating the Withings API yourself are health-data aggregators that list Withings, such as Terra, Thryve, Rook, Spike and the open-source Open Wearables, and the phone health stores, Apple HealthKit and Google Health Connect, which have their own weight and blood-pressure types. An aggregator suits an app that needs Withings beside other devices; the health stores suit a phone app that wants measurements whatever scale or cuff wrote them. Withings' own Public API stays the most direct route, free to start with no prerequisites, as of October 27, 2026.
View as MarkdownPostHacker NewsRedditLinkedIn

Covered here:Health ConnectTerraHealthKitRookSpike

Withings' Public API is free to start: its setup page says "There are no prerequisites, and free access is provided." Teams look elsewhere for other reasons, and this page sets out the realistic options as of October 27, 2026. For the direct build, see the Withings API integration guide.

Why teams look for a Withings API alternative#

  • Limits and paid plans. The standard API allows 120 requests a minute across your application; higher limits and dedicated support are on the Enterprise plan, and some biomarkers need the Advanced Biomarkers plan. The plans page did not render for us, so the price of moving up is unknown until you ask. Withings API pricing has the detail.
  • An unsettled user-side rule. Withings announced that accounts created after October 12, 2026 would need Withings+ to share data with a free-plan app; the notice had left the developer home page by October 27, 2026, and we could not confirm where it stands.
  • One brand. A direct Withings integration covers Withings devices only. An app whose users weigh themselves on several brands of scale needs more than one source.

The alternatives#

Aggregators that list Withings. Several unified APIs name Withings as a source, so it becomes one connection among many:

  • Terra lists Withings as event-driven, with credentials marked "Managed", which Terra's table says means you may create your own credentials and provide them to Terra. See the Terra integration guide.
  • Thryve lists Withings as a web source with historic data, and marks it yes in its Shared oAuth-client column. Terra vs Thryve compares the two.
  • Rook lists Withings as an API source covering body, physical and sleep data.
  • Spike lists Withings on its integrations page.
  • Open Wearables, the self-hosted open-source option, lists Withings as a cloud provider and notes that a Withings account is required and that webhook subscriptions are created per user, not per app. See Terra vs Open Wearables.
  • Sahha lists Withings among sources that arrive on-device through Apple Health or Health Connect.

The trade-off is a recurring aggregator fee and a normalised schema that may not carry every Withings field; health data aggregator pricing compares the bills.

Apple HealthKit and Google Health Connect. Both stores have device-neutral types for what Withings measures. Apple documents bodyMass as "A quantity sample type that measures the user's weight" and bloodPressureSystolic for systolic blood pressure; Health Connect has WeightRecord, which "Captures the user's weight", and BloodPressureRecord. An app that reads these gets measurements from whichever scale or cuff wrote them, on the user's phone, with no Withings developer account. Whether a particular user's Withings readings are there depends on how their Withings app is set up; the Withings developer pages we read do not describe that sync, so treat it as something to test, not promise. See integrating HealthKit, integrating Health Connect, and the blood pressure and body composition data guides.

Withings' contracted solutions. If the Public API is too small rather than too big, Withings itself offers a Cellular Solution, Withings RPM and Logistics Services under contract. Validic, another integration platform, lists Withings Pro cellular devices with the note that approval "requires direct relationship with Withings".

AlternativeBest forWatch out
Terra, Thryve, Rook, SpikeWithings beside many other devicesRecurring fee; normalised fields; check whose credentials each uses
Open WearablesSelf-hosting, no per-user feeYou run it; Withings webhooks are per user
HealthKit or Health ConnectPhone apps that want any brand's weight or blood pressureOn-device only, one platform each, depends on the user's own sync
Withings Cellular, RPMRemote patient monitoring programsA contract with Withings

Which should you pick?#

  • You need Withings and other wearables in one schema. An aggregator. Pick by price and by whether it brokers Withings with its own credentials or yours.
  • Your app lives on the phone and only needs the numbers. Read HealthKit and Health Connect, and treat Withings as one of the sources that may write there.
  • You run a clinical program that ships devices. Talk to Withings about its cellular and RPM solutions before building on the Public API.
  • You only need Withings, at modest volume. Stay direct: the Public API is free to start and its notifications keep you under the rate limit.

The closest comparisons on this site are Dexcom API alternatives for another health-device maker and the wearable data APIs comparison.

Is switching easy?#

Leaving a direct Withings integration means re-mapping Withings' measure types to the new source's fields and asking every user to connect again through the new flow. Moving to an aggregator is a one-time version of that, after which other devices are connect-flow options; moving to HealthKit or Health Connect changes the architecture, from server-side pulls to reads on the phone.

Frequently asked questions

Can I get Withings data without the Withings API?
Through an intermediary, yes. Aggregators such as Terra, Thryve, Rook and Spike list Withings as a source, and Open Wearables connects it in software you host. On the phone, HealthKit and Health Connect have their own weight and blood-pressure types that any scale or cuff app can write to, though whether a user's Withings readings land there depends on their setup.
Which aggregators support Withings?
As of October 27, 2026, Terra lists Withings as an event-driven integration, Thryve as a web source, Rook as an API source for body, physical and sleep data, Spike on its integrations page, Open Wearables as a cloud provider, and Sahha among sources that arrive through Apple Health or Health Connect. Each charges or hosts differently, so compare them before choosing.
Do aggregators need my own Withings developer app?
It varies. Thryve marks Withings yes in its Shared oAuth-client column. Terra marks Withings credentials Managed, which its table explains as meaning you may create your own credentials and provide them to Terra. Open Wearables, which you host, notes that a Withings account is required. Confirm the arrangement with the vendor you pick.
Can I read Withings weight from Apple Health or Health Connect?
Only if the user's Withings app has written it there, which the Withings developer pages we read do not describe. What both stores do document is the type itself: Apple's bodyMass measures the user's weight, and Health Connect's WeightRecord captures it. Reading those gives you weight from any source that writes to them, Withings included when it does.

All 104 questions in Alternatives →

Keep reading

Elsewhere on the site

Pages that share this one’s concepts and sources, from other sections.

Next steps

Was this page useful?

Suggest a correction

Independent comparison, last reviewed October 27, 2026. Pricing, rate limits, and feature availability change often — confirm current details in each provider’s official documentation before you commit. Product and company names are trademarks of their respective owners; AIFitnessAPI is not affiliated with, endorsed by, or sponsored by any product listed here.

← All alternatives · by AIFitnessAPI