Insights on wearable data,
health AI, and open source.
Articles on building with wearable data, health scoring algorithms, and the Open Wearables platform.
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.
What Is an Open Source Wearable API and When Does It Make Sense
An open source wearable API gives you the integration code itself, not just an endpoint. Here is what that means in practice, what Open Wearables provides, and when this approach fits your product.
How to Add Wearable Support to an Existing Health App in Days, Not Months
Adding wearable support to an existing app does not require rebuilding your data layer. Open Wearables sits alongside your backend. Here is what the integration looks like and how long each step actually takes.
How to Give Your LLM Access to Wearable Data
Most LLM integrations with health data dump raw numbers into context and hope for the best. Here is how to use the Model Context Protocol with Open Wearables so your LLM queries the right data and reasons about it.
How to Handle OAuth, Webhooks, and Token Refresh Across Multiple Wearable Providers
Every wearable provider implements OAuth differently, delivers data through a different mechanism, and has different token lifecycle rules. Here is how Open Wearables abstracts all of it and what your application still needs to handle.
How to Build a HIPAA-Compliant Health App That Uses Wearable Data
HIPAA compliance starts with where data lives. Open Wearables is self-hosted: wearable data stays on your infrastructure. Here is what the platform provides and what you need to configure yourself.
What wearable app development actually looks like in 2026
Most tutorials about wearable app development skip the hard parts. This article shows where the complexity actually lives: OAuth flows, token refresh, normalization, webhook-only providers. And what you can take off the shelf with Open Wearables.