Insights on wearable data,
health AI, and open source.
Articles on building with wearable data, health scoring algorithms, and the Open Wearables platform.
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: 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 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 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 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 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.
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.
How to Build an AI Agent That Reasons Over Health Data
An AI agent that reasons over health data is different from one that reads it. Here is how the Open Wearables MCP server works and how to build the reasoning layer on top of it.
How to Add Wearable Data to a Corporate Wellness Platform
Corporate wellness platforms need wearable data from multiple providers without requiring employees to switch devices. Here is what Open Wearables handles and what your application builds on top.
Wearable Data Deduplication: How to Handle Users With Multiple Devices
Users with multiple wearables produce overlapping data. Here is how Open Wearables handles within-provider deduplication automatically and how the priority system resolves cross-provider conflicts.
How to Structure Health Data for AI: What Your LLM Actually Needs
Raw wearable data breaks LLMs. Consistent structure does not. Here is what the Open Wearables data model looks like and how to decide what to pass to your model for each type of health question.
Garmin Connect API: What You Can Fetch and How to Do It Faster
The Garmin API gives you access to workouts, health metrics, and device data. Here is what you can retrieve, how the OAuth 1.0 flow works, and when it makes sense to use a ready-made integration layer instead of building from scratch.
Open Wearables 0.6.3: nap detection and HTTP logs middleware
Open Wearables 0.6.3 adds nap detection for Apple and Oura, structured HTTP logs, an outgoing webhooks flag, and Strava workout samples.
Open Wearables 0.6.2: data integrity for multi-source health apps
Open Wearables 0.6.2 fixes step and energy double-counting for Garmin and Oura, retrieves active minutes natively from four providers, adds sleep session deduplication to the events endpoint, and resolves a Garmin respiratory rate storage bug.
Open Wearables 0.6.1: Data coverage & observability
Open Wearables 0.6.1 adds a Data Coverage tab to the admin panel, introduces PULL_SYNC_LOOKBACK as a safeguard for periodic pull syncs, ships observability and logging improvements, and includes provider-specific bug fixes.