Garmin's Connect Developer Program is paused: what it means if you're building on wearable data
Garmin is a popular health data source for a lot of the apps we see, from training and coaching tools to recovery, research, and corporate wellness products, because many of their users track their days on a Garmin watch. So when Garmin's developer program stopped taking new applications a few months ago, a lot of builders wanted to know what it meant for their plans. This piece covers what has actually changed, what Garmin has said, and what you can do about it today.
What Garmin has said about the pause
By spring 2026, the application form for the Garmin Connect Developer Program had been replaced with an "Under Construction" notice. In a reply on Garmin's developer forums, Garmin's team explained: "The application form for new API access requests is currently unavailable while we complete updates to the Garmin Connect Developer Program. During this transition, new access requests are temporarily paused." Garmin hasn't announced a reopening date or a notification list, so applicants need to keep an eye on developer.garmin.com themselves.
The pause applies to the data API layer, the set of five cloud APIs (listed below) that let a company receive a user's Garmin data on their servers with that user's consent, or send training content back the other way.
What this means in practice depends on where you stand: If you are already approved, the missing form is not evidence that your access has been revoked. Garmin has not publicly announced any shutdown of existing API integrations, so check your own approval, credentials, and connection status to establish where you are.
If you are a new applicant and planning to build a direct integration, the honest advice is to keep Garmin-dependent features off your launch timeline until you have an approval confirmed, because there is currently no channel to apply through. What we do know is that Garmin has publicly signalled that updates to the program are coming. If those end up affecting approval criteria or license rights, every integration will need to review its compliance once the details are published. Terra is working with Garmin as a partner and will fold any new requirements into its integration, so products built on Terra stay compliant with whatever comes out of the update.
It is also worth knowing that the program was never a self-serve signup to begin with. Garmin's program FAQ describes a program built for businesses rather than hobby projects, with an application and review process, and notes that access to some metrics may require a license fee payment or a minimum device order. Garmin's Health API page names enhanced beat-to-beat interval data (the raw millisecond-level heart rhythm signal used for heart rate variability analysis) as one where commercial use requires a license fee.
Users have the right to decide which apps see their health data, and review processes are part of how that consent stays meaningful. The practical consequence for a builder is that access has always taken planning, and right now new applications are not being taken at all.
To be clear about the limits of what anyone outside Garmin knows: we don’t know exactly what changes are coming, and Garmin’s public pages don’t explain why the application form is unavailable or how pending submissions will be handled. What we can see today is that the published terms already leave room for charges: sections 10.1 and 10.2 of the program agreement allow future API fees on 30 days’ notice and charges for request volumes above set limits, and the program FAQ still describes a status response within two business days and a typical integration taking one to four weeks, which does not help an applicant facing a form that is not there.
The missing form is a barrier to applying for new access, not an API outage: on August 19, Garmin published an article about the REACT Wear research project describing automatic data transfer through its Health API and Companion SDK. If Garmin confirms another way to apply, work from that confirmation.
Which APIs the Garmin Connect Developer Program covers
The program covers five cloud APIs, and all five remain listed in Garmin's program documentation through the pause:
| API | What it does |
|---|---|
| Garmin Health API | Daily health data, including sleep, steps and heart rate |
| Garmin Activity API | Data from recorded activities, including FIT files |
| Garmin Women's Health API | Menstrual-cycle tracking and pregnancy information |
| Garmin Training API | Sends structured workouts and training plans to Garmin Connect for users to sync to compatible devices |
| Garmin Courses API | Sends routes to Garmin Connect for syncing to compatible wearables and cycling computers |
The direction of the data matters more than it looks. Importing a completed run and sending next week's workouts to a watch involve different APIs, so "a Garmin integration" is not enough detail to scope a product; you want to know which of the five your features actually depend on. It is also worth understanding the delivery path: the cloud APIs make data available after the user consents and their device syncs with Garmin Connect, so a webhook cannot deliver a measurement that has not reached Garmin Connect yet. If a user sees an old reading, the delay could be in the device sync, the data delivery, or your own processing, and a product needs to tell those apart before asking someone to reconnect their account. Our health data integration lessons go further into the engineering behind reliable delivery.
What Garmin's current requirements mean for your app
Two requirements are worth planning around regardless of when applications reopen.
The first is attribution. Garmin's API Brand Guidelines (the downloadable version is dated June 30, 2025) cover dashboards, detail screens, exports, derived data, and social sharing, and they address outputs materially influenced by Garmin data, including analytics and AI results. Combining Garmin measurements with other inputs does not automatically remove the requirement to credit Garmin. Consider a coaching app that turns a recorded run into a training analysis and lets the athlete download a report: the source needs to remain identifiable through that whole pipeline, because if your data model drops where a measurement came from, the report cannot credit it later.
The second is the difference between developer approval and user consent, because they are separate steps and one cannot substitute for the other. Garmin approving an application gives it access to the program; a user then authorizes sharing their data with that application. A willing user cannot supply the developer approval an app is missing, which is exactly why the paused form matters to new products even when their users are eager to connect. Garmin's Health API documentation describes both steps: evaluation access follows approval, and user data becomes available after consent and a device sync.
Why Garmin API access matters to so many health products
Terra operates the integrations between health products and hundreds of data sources, so we see the same demand from both sides: builders who want to support the devices their users already own, and end users who want to share their data with an app they have chosen.
The end-user side is the one worth dwelling on, because it is where the demand actually comes from. Someone who tracks their training, sleep, and recovery on a Garmin watch increasingly expects to bring that data into the coaching app, the research study, or the health program they have signed up for. They expect the connection to be their choice: they consent, the data flows, and they can revoke it whenever they want. We see that expectation growing steadily on our Garmin integration, and when an app cannot meet it, the disappointment lands on the app. Builders keep Garmin support on their roadmaps because that is where their users' data already lives, and their users are asking for it.
What to do if Garmin was on your integration roadmap
Plan for more than one program. The partners we speak to rarely stop at a single integration, because their users never own a single brand of device. Each manufacturer runs its own program, its own review, its own API shape, and its own maintenance schedule, and those processes are independent of each other. If your users own more than one brand of device, and they do, you are signing up for several of these processes, not one. Because Terra has been a partner with these platforms for years, we can facilitate those processes with you and keep your product compliant as each program evolves.
Terra has maintained a Garmin integration for years as an established partner, which is why Garmin data, including Garmin's own composite metrics (Body Battery, Stress, Training Effect), flows through Terra's data models today, with per-minute detail where Garmin provides it. Users still grant consent through Garmin's own authorization flow, and staying a good citizen of each ecosystem is our full-time job.
Having your sources flow through one set of data models also opens up more than reading a single device ever could: sleep, activity, heart data, and lab and blood results arrive in the same shape regardless of where they came from, and the connection writes as well as reads, so products can push planned workouts and routes to a user's watch too.
The bigger picture: developer access across the industry is changing shape
Garmin's pause is one move in a broader reshaping of how health and fitness platforms grant data access. Strava updated its API agreement in November 2024, changing how third-party apps may display and process user data. Google retired the Google Fit REST API in June 2025 and launched its successor, the Google Health API, in March 2026, with the legacy Fitbit Web API scheduled to wind down in September 2026. Several other manufacturers run partner-based or approval-based access as their standard model. We wrote about the Strava changes and the Google Health API in more depth separately.
For a builder, the practical read is that direct API access across this industry is something you plan around, with timelines you don't control. Terra is the infrastructure partner that keeps your product compliant and in line with each platform's changes as they come.
If you want to see what Garmin data looks like through Terra, the docs show the full data model, and you can try it against sample data before you connect a single real user.
