Garmin has quietly stopped letting new developers into its cloud platform. The Garmin Connect Developer Program, which gives companies access to Health, Activity, Training, Courses and Women's Health API data, is closed to new applicants, and Garmin is not saying when it will reopen.
The company's own words, sent to applicants who ask, are these:
We are currently evolving and modernizing the Garmin Connect Developer Program. During this transition, we have temporarily paused the review and approval of new API access requests.
That message comes with three details developers have confirmed on Garmin's own forums, and they are the whole story:
- The application form for new partners has been removed.
- New API access requests are paused, with no projected reopening date.
- There is no notification list. Garmin told one applicant that status updates will appear only on developer.garmin.com, and that applicants should monitor the page themselves.
So there is no timeline and no way to be told when there is one. You just have to keep checking.
The Official Page Still Invites Applications
Here is the part that has developers frustrated. Garmin's Program FAQ still reads: "If you are interested, please request the Garmin Connect Developer Program and we'll quickly review your application."
The form is gone. The quick review is not happening. The program overview page now carries a single line of guidance: "Stay tuned for more updates on the program."
What Developers Are Actually Experiencing
The forum threads tell the story better than the policy language does.
A founder building an AI-powered health and wellness app submitted an access request on March 1 for read-only Health API data: steps, sleep, heart rate, stress, body composition. Garmin's partner services team responded within a day, asked for background, then asked for a website and privacy policy. Both were provided, and on March 5 he was told the request was "successfully verified" and in the approval process, which the FAQ describes as up to two business weeks.
He followed up on March 23, March 31 and April 4. No response to any of them. He eventually learned through an unrelated channel that the request had been rejected. He was never notified, and never given a reason.
Another developer submitted twice. The first attempt was rejected because the privacy policy was on the app page rather than the business page, which he fixed. The resubmission was confirmed received, and then sat for nearly five weeks in silence, against an FAQ that promises two business days for a status confirmation.
A third has been using Garmin devices for a decade and wanted to build his own training analytics platform with Health, Activity and Training API access. "Seems that my data finally does not belong to me as Garmin keep all my data," he wrote.
And a small EU running and nutrition coaching app applied in the spring, got the official paused-with-no-date reply, and has since changed strategy entirely: "We're going Connect IQ first. The Connect IQ developer experience itself is fine. It's only the cloud-side API that's blocked for us."
What This Means for Developers
The distinction that matters is on-device versus cloud.
Connect IQ is unaffected. That is Garmin's SDK for building apps and watch faces that run on the watch itself. The EU developer above is still building for Forerunner, Fenix, Epix, Venu and Vivoactive hardware. Nothing about that path has changed.
The cloud API is the door that closed. The Connect Developer Program is what lets a third-party service pull your Garmin data into its own platform. That means coaching apps, nutrition tools, training analytics dashboards, and AI assistants that want to reason over your sleep and HRV history. Existing partners keep working. Nobody new is getting in.
Long-time community members on the Garmin forums are blunt about what they think is going on. "It seems Garmin gives this access to a very limited number of companies (big ones)," one wrote, adding that he tried getting access years ago. Another: "Garmin never made this API widely available."
That reading is supported by Garmin's own FAQ, which states the program is "available for enterprise use" and "only for business use," and that "access to some metrics may require a license fee payment or minimum device order quantity for commercial use."
Is Garmin Narrowing the Program on Purpose?
Garmin is calling this a modernization. Reporting on the pause describes an internal "significant redesign" of the whole program. That is a real possibility, and so is the less flattering one: that Garmin is quietly converting an open-ish developer program into a commercial partnership tier.
Three things in the timeline make the second reading harder to dismiss.
Strava sued Garmin over API terms. Strava filed a federal patent infringement suit against Garmin on September 30, 2025 in the District Court of Colorado, over Strava Live Segments and heatmap routing, and demanded that Garmin stop selling virtually all of its fitness devices. Strava argued Garmin had gone beyond the scope of the Master Cooperation Agreement the two companies signed, which included a clause that Garmin would not show Garmin and Strava Segments at the same time. Twenty-one days later, Strava voluntarily dropped the case without explanation.
The suit is over. The lesson for a hardware company that depends on software partners is not.
Garmin bought TrainingPeaks and TrainHeroic. In July, Garmin acquired two of the biggest coaching platforms in endurance and strength sports. TrainingPeaks in particular sits at the center of the third-party coaching ecosystem, and Garmin now owns it. When the company that controls the API also owns a major consumer of that API, "we're modernizing the program" reads differently than it would otherwise.
Garmin already has a paid data product to protect. Connect+ launched as a subscription with AI-driven insights, and it took immediate backlash from users who felt a paid tier was being carved out of features that used to be free. Anything that hands raw Garmin data to an outside AI platform is, at minimum, adjacent to what Connect+ sells.
The MCP Question
This is where the developer freeze runs straight into where the industry is going.
A Garmin owner and scientist posted a formal request on Garmin's forums asking the company to build a Model Context Protocol integration with Claude. His argument was clean: Garmin Connect already collects one of the richest longitudinal datasets in consumer health, including Body Battery, HRV, sleep architecture, pulse ox, training load and stress, and what it lacks is interpretive analysis. MCP is the open standard for exactly that, and Google Drive, Gmail and Microsoft 365 had already shipped connectors.
The response from Garmin was silence. A forum moderator's only reply was that the request was in the wrong place and should go through Garmin's ideas portal instead.
Where Garmin has not gone, its users have. Community MCP servers that pull Garmin Connect data are already out there, including Taxuspt's garmin_mcp, a read-only server for Claude Desktop, and a workout-management server that exposes training and coaching workflows. Developers have built hosted bridges for the same purpose. One forum member said he had been running an MCP integration with Claude for over a month and that its advice beat Garmin's.
There is an obvious conflict Garmin has to weigh. As one developer put it in the same thread, an MCP connection "competes with some features in Connect+." Others said the opposite of what a subscription-first company would hope: several users said they would happily pay to connect their own data to Claude, and one said flatly that he would not pay for Connect+ just to get his own data out.
COROS Already Did What Garmin Won't
The contrast is not hypothetical.
In May, COROS launched the first officially supported MCP server from a major sports watch brand. It exposes a single endpoint at mcp.coros.com/mcp, works with Claude Pro, ChatGPT Plus and Cursor, and is read-only by design at launch, covering activities, daily health metrics, sleep and HRV, EvoLab assessments and your current training plan. COROS has publicly flagged write permissions, meaning AI-generated training plans landing in your calendar, as the next step.
The part Garmin should find uncomfortable is how COROS handled developer access. COROS runs a self-service developer path using OAuth 2.0 that, by its own documentation, requires no application approval, offering read access to 22 documented data fields plus the ability to write training plans. Approval and review are reserved for platforms serving multiple users commercially.
COROS says inbound API integration requests grew by more than 1,100% over the past year, and that rather than routing that demand through an approval process, it opted for the open standard.
Set that against Garmin's removed form, absent notification list and unnamed reopening date, and the two companies are making opposite bets about who should control your training data.
What This Means for Your Data
Practically, here is where things stand.
Nothing you already use should break. Existing API partners keep their access. Your watch still syncs, and Connect+ still works.
New integrations are on hold indefinitely. If you were waiting for a third-party coaching app or analytics tool to add Garmin support, that is not coming until Garmin reopens the program, and nobody outside Garmin knows when that is.
Connect IQ is still open. Developers who can run their idea on the watch itself are unaffected, which is why at least one coaching app pivoted there.
Your data is still yours to export, technically. Garmin lets you download your own data, and your activities sync to whichever platforms you have already connected. That is a manual path, not an API, but it exists.
Set a reminder to check. Since Garmin has no notification list, the only way to find out when this ends is to watch developer.garmin.com yourself.
Bottom Line
Garmin has closed its cloud API to new developers, removed the form, given no reopening date, and built no mechanism to tell anyone when it changes. It calls this modernization. Around the same time, it bought TrainingPeaks, and it is now selling AI health insights through Connect+ while declining to answer the MCP question at all.
The most generous reading is that Garmin is rebuilding the program properly and it will reopen better than before. The less generous one is that the era of building a business on Garmin data is ending for everyone except a short list of approved partners.
Either way, developers are currently applying to a program whose own FAQ promises a response the program is no longer giving. Until Garmin says otherwise, if you want your Garmin data in someone else's AI, the answer is going to come from COROS before it comes from Garmin.
Sources: Garmin's Connect Developer Program overview and Program FAQ pages (developer.garmin.com), Garmin forum threads documenting the pause, including the Garmin Connect Developer Program access-request thread and the MCP integration feature request, the5krunner's reporting on the developer API pause (September 14, 2026), Momentum's analysis of the program pause, COROS's official MCP documentation (coros.com) and the coroslab/COROS-MCP repository, Android Authority's COROS MCP coverage, Front Pack Sports on the 1,100% growth in COROS API requests, Strava's September 2025 patent suit against Garmin as reported by BikeRadar, NPR and Lifehacker, and our own coverage of Garmin's TrainingPeaks and TrainHeroic acquisition.