What shipped, and how to build with it.
Release notes every couple of weeks, guides to the provider APIs and their quirks, and the occasional longer piece on getting health data into a shape you can work with.
Posts
Releases · · 11 min read
Open Wearables 0.10.0: new dashboard, nutrition data and sync-aware webhooks
Open Wearables 0.10.0 rebuilds the dashboard in SvelteKit, adds 42 nutrition series types with a meal event, tags every data webhook with the sync it came from and splits calories into total, active and basal energy. Contains breaking changes.
Guides · · 9 min read
Moving from a hosted wearable API to Open Wearables: a migration playbook
Moving from a hosted wearable API to Open Wearables is usually a re-integration rather than a data migration. This playbook walks through the decisions, the steps in order, how your users reconnect and what to tell your security team.
Guides · · 7 min read
Why teams move from a hosted wearable API to Open Wearables
A hosted wearable API is a sensible way to start. As a product grows, the questions change: whose provider apps, whose cloud, whose schema. Here is why teams move to Open Wearables, what they get after the move, and what it asks of them.
Garmin · · 4 min read
Garmin Connect Developer Program reopened: what changes for your integration
Garmin reopened the Connect Developer Program with Personal, Starter and Enterprise tiers. Each company now holds its own app and credentials. Here is what that means for delivery, backfill, AI use and moving an existing integration.
Releases · · 13 min read
Open Wearables 0.9.0: Google split into two providers, energy renamed, and a long list of API corrections
Open Wearables 0.9.0 splits Google into google_health and health_connect, renames energy to active_energy, disables the Google Health API rollup that wrote duplicated rows, and fixes date bounds, filters and pagination across the API. Contains breaking changes.
Releases · · 10 min read
Open Wearables 0.8.0: Withings, sync history, and faster ingestion
Open Wearables 0.8.0 adds Withings, database-backed sync history with two new endpoints, a 3.7x faster bulk upsert path, 5 GiB Apple Health XML uploads with MinIO parity, and four account takeover fixes.
Releases · · 7 min read
Open Wearables 0.7.0: Google Health API, Sensor Bio, and a faster Admin UI
Open Wearables 0.7.0 adds a Google Health API integration ahead of the Fitbit Web API sunset, a new Sensor Bio provider, finer Oura sleep granularity, and Admin UI and logging improvements.
Google Health API · · 6 min read
Google Health API: A Practical Guide to Getting Started
A step-by-step walkthrough of setting up the Google Health API: Google Cloud project, OAuth client, environment variables, and verifying your first synced data.
Google Health API · · 6 min read
Google Health API and Google Health Connect: What's the Difference
Google runs two separate products under the same name. Health Connect lives on the device and needs an SDK. The Google Health API is a cloud REST API and needs OAuth verification and CASA at scale.
Fitbit · · 6 min read
Fitbit Alternatives for Developers
Fitbit is shutting down its Web API in September 2026. Here is how to think about replacement data sources as a developer, not as a consumer buying a new watch.
Fitbit · · 7 min read
Fitbit Web API Shutdown 2026: Migration Guide
Google is turning down the legacy Fitbit Web API in September 2026. Here is what still works, what never did, and how the migration to the Google Health API actually looks.
Google Health API · · 10 min read
Google CASA and OAuth Verification for Health Apps
Moving to the Google Health API means OAuth verification and an annual CASA security assessment. Here is what it costs, how long it takes, and why self-hosting does not move the responsibility off your organization.
Guides · · 5 min read
How Wearable Data Flows From Device to Your API: A Complete Architecture Guide
Wearable data does not go directly from device to your API. It flows through the provider cloud, then Open Wearables, then PostgreSQL, then your application. Here is what each step looks like.
The platform