Garmin appears to have stopped processing new applications to the Garmin Connect Developer Program sometime in spring 2026, according to reports from developers and correspondence seen by the5krunner.
The application form has disappeared from Garmin’s developer website. Instead, the programme page now says: “Stay tuned for more updates on the program.”
Our Research
Several developers who applied around March and April say Garmin Connect Partner Services told them that new API requests had been paused while the programme was being updated.
Cycling analytics platform CycleLytic applied on 2 March 2026 and shared its full ticket history with the5krunner.
- 2 March 2026 — Garmin verified the application and said it had entered the approval process. The expected wait was two business weeks.
- 30 March 2026 — Garmin changed that to “a few business weeks”.
- 12 May 2026 — A separate request for Training API access was told that the application form was unavailable while Garmin completed updates to the Connect Developer Program.
- 20 May 2026 — After CycleLytic escalated, Garmin said it was working on a “significant redesign and modernisation of the API program and related processes”. It also said it could not process new requests already in the queue and could not say when processing would resume.
- 11 September 2026 — CycleLytic’s March application was still waiting for a decision.
In other words, CycleLytic appears to have applied before Garmin stopped processing new requests, but its application then got stuck in the queue.
Training platform Blocks, a structured-workout builder and training calendar with about 1,300 registered athletes, reports a similar experience. It applied for Training and Activity API access on 16 July 2026 and, in mid-September, received a reply that new connections are not being accepted, with no timeline given. Blocks says Wahoo and Hammerhead approved its integration requests within weeks, self-serve. In the meantime, its Garmin users are routed through intervals.icu as a bridge, or given FIT files built to match Garmin’s own cookbook so that structured workouts still show pace targets on the watch.
Existing approved partners continue to work.
This does not affect Connect IQ, which remains open. Garmin released Connect IQ 9.2.0 on 25 August 2026.
There is also a problem with Garmin’s own documentation. The Connect Developer Program FAQ still says new applications are normally confirmed within two business days.
That clearly does not match what developers are being told now.
What this means
- Garmin owners using existing integrations see no announced change.
- Manual export still works, including individual FIT files and Garmin’s bulk account export.
- For developers, the public route for getting new Connect API access is currently closed.
CycleLytic says its Garmin integration is already built and deployed. It has a webhook endpoint, file parser and storage, alongside working integrations with Strava, Wahoo, ROUVY, Suunto and Hammerhead.
But it has never received a Garmin activity because Garmin has not approved its API access.
Wahoo‘s Cloud API, by comparison, has no reported equivalent pause. For a developer choosing where to build today, Garmin is therefore a difficult platform to target.
Why is Garmin doing this?
We don’t know.
Garmin says it is carrying out a “significant redesign and modernisation of the API program and related processes”. That tells us a major change is underway.
One possible reason is that Garmin is changing the rules about what developers can do with Garmin data, including how they can use it for AI and machine learning.
- In July 2025, Garmin introduced API Brand Guidelines requiring Garmin attribution when Garmin data appears on third-party services.
- Strava then sued Garmin over several issues, including Garmin’s API terms and attribution requirements. Strava dropped the lawsuit three weeks later without publicly explaining the settlement.
- Strava had already tightened its own API rules in November 2024. Those changes included restrictions on using Strava data to train AI or machine-learning models.
That makes changes to Garmin’s own data-use rules a plausible explanation. But it is only a theory. Garmin has not said this is what it is doing.
Strength-training app Hevy says Garmin rejected its application for full API access and directed it towards Connect IQ instead.
We don’t know when Garmin made that decision, so it is not evidence of the current pause. It does, however, show that Garmin has restricted some third-party access in the past.
There is another possible explanation.
- Garmin has acquired Tacx, Firstbeat, MYLAPS and, in July 2026, TrainingPeaks and TrainHeroic.
- Garmin now has more products, services and data systems to manage. Bringing all of this together could require a major overhaul of how developers apply for access, how access is approved and how data can be used.
- Garmin may simply be rebuilding a developer programme that has become complicated to run.
There are other obvious reasons too. Running a public API creates support costs and privacy and security responsibilities, especially when the data includes health and activity information.
A reason for developers to be cautious
Garmin bought Firstbeat in 2020 and said third-party licensing would continue. Since then, obtaining new Firstbeat licensing has become more difficult.
The comparison is not exact but it is a useful reminder that third-party access can change over time, even when a company initially says it will continue.
Connect IQ is not the same thing
Connect IQ is for apps, watch faces and data fields that run on Garmin devices. Whereas the Connect Developer Program is the route used by cloud services that need access to Garmin activity and health data.
Strava is one workaround
One common route is:
Garmin > Strava > third-party service
This allows a service to get Garmin activities indirectly, rather than connecting to Garmin itself.
Yet, Strava has tightened its API rules twice since November 2024. If it tightens them again, some services could lose an important way of getting Garmin activity data.
What happens next?
Garmin announced its acquisition of TrainingPeaks and TrainHeroic on 22 July 2026, several months after the developer pause began.
So the acquisition did not cause the original pause, although it may be part of why Garmin is now reviewing how its different products and services work together.
The main unanswered question is simple:
What will Garmin replace the current developer programme with, and when will it allow new developers back in?
Quick answers
Is the Garmin Connect Developer Program still open?
No. Garmin appears to have stopped processing new applications by spring 2026 and has removed the application form. Existing approved integrations continue to work.
Does this affect Connect IQ?
No. Connect IQ is a separate programme for watch faces, data fields and apps running on Garmin devices.
Has Garmin said when the programme will reopen?
No. Garmin’s private replies describe a “significant redesign and modernisation” and give no estimated date for resuming application processing.
Last Updated on 24 October 2026 by tfk the5krunner
Small things I always use
- Garmin 90-degree charging adapter: Charges your Garmin from any USB-C cable. Essential when travelling. I use one.
- Body Glide: The blue anti-chafe stick swimmers and runners carry. I use it.
- Speedo earplugs: Fewer ear infections and no cold-water dizziness. I use them.
- Dryrobe Advance: My winter changing robe for open-water swims. I use one. A cheaper option is the AONYIYI changing robe.
- Maurten: Race fuel that stays easy on the stomach. I use them.
- Beet It Sport nitrate shots: Beetroot shots I take in the days before a race. I use them.
- Garmin charging puck: The quickest way to top up before a session. I use one.
- Injinji: Toe socks that stop rubbing, so you run more. I use them.
- Ultimate toe protectors: Stop black toenails on long runs. They work. I use them.
- Compressport R2 v2 calf sleeves: My calf sleeves of choice. I use them.
- Cellucor C4: My pre-workout before hard sessions.
- TPU tubes: Schwalbe Aerothan, Tubolito and Pirelli SmarTube. Light, tiny spares. I use all three.
- G8 insoles: Adjustable insoles that are good. I use them.
- Cycplus Cube: A 97g electric pump that gets a road tyre rideable in two minutes. I carry one. 5% off with code THE5KRUNNER.
Watches and sensors
- Polar H10: My daily driver for waking HRV.
- Polar Verity Sense: My backup arm-worn HR sensor.
- Nomad bedside charger: Charges my iPhone and Apple Watch overnight. I use it, and many of their bands.
- Train.Red: The best muscle oxygen sensor I’ve used.
- Tymewear: Accurate heart rate and reliable ventilatory zones. I use it to pace endurance rides over an hour.
- Garmin Forerunner 970: A pro-grade triathlon watch. I use this.
- Apple Watch Ultra 4: My daily smartwatch. No phone needed on rides.
- Garmin Fenix 9 Pro: I’ve just bought one.
On the bike
- Continental GP5000 for everyday riding, and Aero 111 on the front for special occasions.
- Helmets: Specialized S-Works Evade 3 for road riding, and Rudy Project Wing for TT-style races. I use both.
- Ravemen FR300: A front light that mounts under your Garmin or Wahoo. I use one.
- Wahoo TRACKR Radar: I use it on one bike and Varia on the other. They perform the same.
- Garmin Varia RTL515: Radar that warns you of cars from behind. I use this model.
- Wahoo ELEMNT Roam 3: The bike computer that’s easy to use. I use mine on most rides.
- Favero Assioma Pro RS2: Accurate power pedals that swap easily between bikes. I use this model.
Home and indoor training
- NPE Runn: Makes my basic treadmill smart, sending more accurate speed and distance to my watch and Zwift. I use it.
- Google Wifi: Keeps Zwift connected in my pain cave. I use it.
- Apple TV 4K: Zwift on the big screen. I use two.
- Google Nest Doorbell (wired, 2nd gen): My video doorbell, running in both Google Home and Apple Home. I use it.
Health, recovery and sleep
- FreeStyle Libre 3 Plus: Shows how my blood sugar responds to diet.
- hDrop: Measures my sweat loss in summer and indoors.
- Fourth Frontier Zone: Checks my heart under load in hard sessions.
- Oura Ring 5: My partner’s recovery tracker of choice.
- Eight Sleep: A cooling mattress cover my partner and I use nightly.
Reader-Powered Content
This content is not sponsored. It’s mostly me behind the labour of love, which is this site, and I appreciate everyone who supports it.
Support the site: Follow (free, fewer ads) · Subscribe (paid, ad-free) · Buy Me A Coffee
Written by real people, with AI assistance. Fact-checked and verified for originality. See the Editorial Policy. FTC: Affiliate Disclosure — some links pay commission. As an Amazon Associate, I earn from qualifying purchases.
tfk is the founder and author of the5krunner, an independent endurance sports technology publication. With 20 years of hands-on testing of GPS watches and wearables, and competing in triathlons at an international age-group level, tfk provides in-depth expert analysis of fitness technology for serious athletes and endurance sport competitors. See the gear tfk uses. ID
I’ve built a running app that gives user realtime AI coaching and insights during their run sessions. I experienced the same issues with Garmin earlier this year. All of a sudden just changed their criteria after having a staging app and then just refused to review the production request! It was infuriating!
Drop me an email if you want to discuss further.
I don’t know exactly what the Garmin API actually provides, but unless an app needs something like realtime metrics while an activity is in progress, then it maybe doesn’t need any provider specific integration like Garmin. There is HealthKit on iOS and Health Connect on Android and 3rd party apps can query and utilise this data. This might even be advantageous in some scenarios, since if the user is using multiple apps to log different activities, you can combine, aggregate, compare, etc, data from multiple sources.
Yeah, HealthKit is quite settled on iOS, but is Health Connect on Android? Do we, as users, want all our activity data pushed from Garmin to Google in order to simplify work for third party devs?
When you push a coros activity to apple health, it does not send the mapping points and so when extracting / querying from apple health to your app, you don’t get a route of a run for example. That is one of many issues.
What a sad state. I just need route push, no PII health data nightmare, no strategic considerations regarding competing analytics platforms. The way I see it Garmin are just donating a free moat to route management incumbents like Komoot or Strava who surely won’t return any favors.
“and directed it towards Connect IQ instead” – this reads a lot like throwing hands in the air “we don’t know if the team who claimed responsibility for API legals will ever continue what they started, you know as much as we do”. Likely some legal team who vigorously threw themselves between engineers and API at some point to demonstrate importance and then promptly forgot everything about if….