Garmin is on the roadmap.
Garmin is planned. Its Health and Activity APIs are open to approved business developers through the Garmin Connect Developer Program, so a self-hosted instance can't use them on its own.
- 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 would collect.
What Garmin offers developers, as listed in the connectors table. The final connector may cover less.
- Daily summaries
- Sleep
- Stress
- Heart rate
- Activities
How it would work.
Once the connector is built, the same way every other source works today.
- 01
The user connects
Your server asks for a consent URL and sends the user to Garmin. Tokens are stored encrypted.
- 02
The server pulls
A first backfill, then scheduled pulls, and webhooks where the provider sends them. Every raw payload is kept.
- 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.
- Garmin's developer agreement bars publishing an integration without its consent, so the connector waits for Garmin's answer.
Want it sooner?
Connectors are self-contained: one package that maps a provider into the same model. Tests use recorded fixtures and a fake of the provider's API, so no real account is needed to build one.
Questions.
Can I use Garmin with Open Health Sync today?
Not yet. Garmin is on the roadmap and no code for it runs today. The planned path: Partner program (Garmin Connect Developer Program), OAuth 2.0 with PKCE, Garmin pushes notifications.
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.
How can I get it sooner?
Connectors are self-contained. The guide on writing a connector walks through one, and an issue on GitHub tells the maintainers it matters to you.