Garmin reopened its developer program. Check whose key you're on.
GARMIN CONNECT
Garmin reopened its developer program. Check whose key you're on.
Garmin reopened its Connect Developer Program on 21 October after months closed to new applications. There is a personal key for your own data, a Starter tier for organisations building their first apps, and an Enterprise tier for scale. Enterprise moves to per-user billing, reported to start on 1 April 2027.
The rule that matters more than the tiers. Garmin's developer agreement doesn't allow passing keys or data to a third party without written permission. Each company is expected to register its own app. Strava wrote a similar rule on API tokens into its agreement in June, and several platforms have already asked customers to bring their own Garmin credentials.
If you run Open Wearables, you already work this way. Your deployment uses your own Garmin app and credentials, and the data stays in your infrastructure. Nothing changes on our side. If you are still on a pending application, now is a good time to reapply under the new tiers.
Two things to check this week:
Starter is push only and has no historical data. If your onboarding shows a new user their past weeks, plan for Enterprise.
The updated agreement rules out training your own AI models on Garmin data. Using a model to answer a user about their own data, with consent, appears to remain allowed. Check the agreement with your counsel.
If you're moving a Garmin integration from someone else's key onto your own and want a hand, reply to this email.
Open Wearables team
openwearables.io · Docs · GitHub · Discord
Built and maintained by Momentum