Open Wearables 0.7.0: Google Health API

Table of Contents

Heading

EXCLUSIVE LAUNCH

AI Implementation in Healthcare Masterclass

Start the course

Key Takeaways

Google is turning down the legacy Fitbit Web API in September 2026. Open Wearables' new Google Health API integration is the migration path: it aggregates data from a user's entire Google Health account, including Fitbit and Google Fit.
Because of the sunset, Open Wearables' Fitbit integration is now feature-frozen: still supported as-is, but no further development.
Migrating isn't automatic: existing Fitbit tokens can't be reused, so each user has to re-consent through Google OAuth.
Sensor Bio joins as a new provider (workouts, sleep with stages, recovery, 24/7 biometrics).
The release also brings finer-grained Oura sleep data, a faster Admin UI, clearer data provenance, per-provider data deletion, and more resilient sync logging.

Is Your HealthTech Product Built for Success in Digital Health?

Download the Playbook

Open Wearables, our open-source health data platform, just shipped version 0.7.0. The headline addition is a new integration with the Google Health API, alongside a new Sensor Bio provider and a set of improvements to the Admin UI and backend logging.

Why the Google Health API Matters Right Now

Google is deprecating the legacy Fitbit Web API. According to Google's own developer documentation, the Fitbit Web API will be turned down in September 2026 and will no longer sync data to or from Fitbit users. Any product that pulls data from Fitbit through that API has a deadline: migrate to the Google Health API, or lose that data source entirely.

Open Wearables' Fitbit integration is now feature-frozen for that reason. It stays available and supported as-is, but no new data types or features will be added to it. The path forward is the new Google Health API integration.

That integration works as an aggregation layer: it pulls data from every source connected to a user's Google Health account, not just one device. That includes Fitbit, Google Fit, and other connected apps, surfaced through a single OAuth connection to the user's Google account. Supported data types span steps, distance, calories, hydration, heart rate, resting heart rate, HRV, VO₂ max, respiratory rate, SpO₂, weight, body fat, core body temperature, blood glucose, workouts, and sleep with stages, delivered either by polling or by notify-only webhooks.

One migration detail worth flagging for anyone planning ahead: existing Fitbit OAuth tokens can't be carried over to the Google Health API. Every user whose Fitbit connection you want to preserve will need to re-consent through Google OAuth before the September 2026 deadline.

Open Wearables also solves a data-quality problem that comes with aggregating multiple sources: when a phone and a Fitbit both track the same walk, you get two step counts for the same window. The integration defaults to a "reconcile" mode that merges and deduplicates across sources to match what the native Google Health or Fitbit app shows, rather than arbitrarily picking one source's number.

A Second New Provider: Sensor Bio

0.7.0 also adds Sensor Bio as a new provider, connected via OAuth 2.0 with pull-based syncing. Sensor Bio's own API doesn't currently offer webhooks, so this integration is polling-only. It brings workouts, sleep with stage breakdown, recovery scores (resting heart rate, HRV, SpO2), and continuous 24/7 biometric timeseries into Open Wearables' unified data model.

Sharper Oura Sleep Data

Oura sleep stages are now synced at 30-second granularity, up from the previous 5-minute granularity, giving more precise sleep stage timing for Oura users.

Making the Platform Easier to Run and Operate

The rest of 0.7.0 is about running Open Wearables at scale:

A faster Admin UI. The dashboard could previously take several seconds to load on constrained infrastructure. Front-end optimization work means it now loads near-instantly, even with large data volumes and limited RAM, and now shows more detail about stored data volume and type.
More visibility into data provenance. Workouts, sleep sessions, menstrual cycles, and activity data now show not just which provider synced the data, but the original source and device where applicable (for example, when Apple Health surfaces data synced from a non-Apple device).
Per-provider data deletion. Users can now delete all data tied to a specific provider from their profile, which also disconnects that provider automatically.
SDK application management in Settings, directly from the Admin UI.
More resilient sync logging. A single malformed row in an SDK sync batch no longer takes down the entire batch; Open Wearables now reports and logs the specific failing rows while keeping the rest of the batch intact. Logs also carry more diagnostic detail for tracking down sync issues in production.

Open Source, Self-Hosted, Still Moving

Open Wearables remains MIT-licensed and self-hosted: teams run it on their own infrastructure rather than routing health data through a third party. Official Docker images are available for both backend (themomentum/open-wearables-backend) and frontend (themomentum/open-wearables-frontend).

The full 0.7.0 changelog is on GitHub, and setup guides for the Google Health API and Sensor Bio integrations are in the documentation.

Frequently Asked Questions

Why is Open Wearables freezing its Fitbit integration?

Google is turning down the legacy Fitbit Web API in September 2026. Since that API is going away, there's no path to keep extending an integration built on it. The Fitbit integration stays available and supported as-is, but new development is going into the Google Health API integration instead, which already surfaces Fitbit as one of its data sources.

Will my users' existing Fitbit connections keep working after the switch?

Not automatically. Existing Fitbit access and refresh tokens can't be reused with the Google Health API, so each user needs to reconnect through Google OAuth to keep their data flowing.

What does the Google Health API actually aggregate?

Everything connected to a user's Google Health account: Fitbit, Google Fit, and other connected apps, through one OAuth connection.

Is Sensor Bio a replacement for another provider, or new coverage?

It's a new provider addition, bringing workouts, sleep with stage breakdown, recovery scores, and continuous 24/7 biometrics into Open Wearables for the first time via that vendor.

Is Open Wearables still open source and self-hosted?

Yes. Open Wearables is MIT-licensed and runs on your own infrastructure via official Docker images for backend and frontend.

Written by Bartosz Michalak

Director of Engineering

He drives healthcare open-source development at the company, translating strategic vision into practical solutions. With hands-on experience in EHR integrations, FHIR standards, and wearable data ecosystems, he builds bridges between healthcare systems and emerging technologies.