---
title: "Blog, page 2"
description: "Older posts from the Open Wearables blog, page 2: release notes, provider API guides and building with self-hosted health data."
canonical_url: "https://openwearables.io/blog/page/2"
---

# What shipped, and how to build with it.

Blog

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.

[Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book)

## Posts

Guides · Jul 22, 2026 · 5 min read

### 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.

Guides · Jul 22, 2026 · 5 min read

### 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.

Guides · Jul 22, 2026 · 5 min read

### 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.

Guides · Jul 22, 2026 · 6 min read

### 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.

Guides · Jul 22, 2026 · 5 min read

### 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.

Guides · Jul 22, 2026 · 5 min read

### 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.

Garmin · Jul 21, 2026 · 8 min read

### 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.

Guides · Jul 21, 2026 · 6 min read

### 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.

Guides · Jul 21, 2026 · 8 min read

### 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.

Guides · Jul 21, 2026 · 4 min read

### 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.

Releases · Jul 16, 2026 · 5 min read

### 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.

Guides · Jul 15, 2026 · 8 min read

### 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.

The platform

## Looking for the product rather than the post?

### [Platform](https://openwearables.io/platform)

### [Integrations](https://openwearables.io/integrations)

### [Pricing](https://openwearables.io/pricing)
