Skip to content
Open Health Sync
Open Health Sync on GitHub (opens in a new tab)Sign inGet started for freeStart free
All integrations
Built, in the next release

Garmin data, in your own stack.

The Garmin connector is built and comes in the next release. It reads Garmin's official Health and Activity APIs, which are open to approved business developers through the Garmin Connect Developer Program, so a self-hosted instance needs that access first.

Read the setup guideTracking issue #9 (opens in a new tab)
Source
Watches and cycling computers
How the data arrives
Partner program (Garmin Connect Developer Program), OAuth 2.0 with PKCE, Garmin pushes notifications.

What it collects.

Each record maps to the same model as every other source, with the provider, source and device it came from.

  • Daily summaries
  • Sleep
  • Stress
  • Heart rate
  • Activities

How it works.

  1. 01

    The user connects

    Your server asks for a consent URL and sends the user to Garmin. Tokens are stored encrypted.

  2. 02

    The server pulls

    A first backfill, then scheduled pulls, and webhooks where the provider sends them. Every raw payload is kept.

  3. 03

    You read one model

    Units, time zones and duplicates handled, served over REST, the read-only MCP server and FHIR R4.

Before you start.

  • For approved business developers only, and some data needs a commercial license fee.
  • Per Garmin's replies to applicants, new access requests have been paused since spring 2026, with no public reopening date.
  • Not usable by an individual running their own instance.
  • Built on the official APIs only: Garmin pushes notifications and the connector pulls the summaries they point to.

Set it up.

Register your own Garmin app, set its callback to <OHS_PUBLIC_URL>/oauth/garmin/callback and put its credentials in .env. The guide has every step. This connector is on main: build from source until the next release.

Terminal
# .env# Ask for a consent URL, then send the user to authorize_urlcurl -s -X POST $OHS/v1/users/$USER_ID/connections/garmin \  -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' \  -d '{"redirect_uri":"https://app.example.org/connected"}'# Read what came incurl -s "$OHS/v1/users/$USER_ID/undefined" -H "Authorization: Bearer $KEY"

Questions.

Can I use Garmin with Open Health Sync today?

Not in a release yet. The connector is built and merged on main, and comes in the next release. You can build from source to try it now.

Do I need anything from Garmin?

For approved business developers only, and some data needs a commercial license fee.

Where does the data go?

Only to the server you run. Open Health Sync is self-hosted software, not a service: no account with us and no call home. Each user can be deleted with one call, raw files included.