For years, getting your own Garmin data out of Garmin Connect meant either wrestling with unofficial libraries or pretending to be a company. That changed this week.
Garmin has reopened its Connect Developer Program after seven months of turning new applicants away, and it rebuilt the whole thing around three tiers. The one that matters to most people is the new Personal API, which hands individual athletes a key to their own account without an approval queue, a business case, or a legal entity.
Garmin's own developer site describes it plainly: secure access to your own Garmin Connect data for "individuals who want to explore, analyze, and build personalized experiences using their own data."
How the Personal API actually works
The setup is genuinely fast. You log into Garmin Connect on the web, go to the Personal API Key page, hit Create Key, accept the terms, and pick an expiration window. Garmin's FAQ says the key is displayed exactly once, and if you lose it you delete it and start over.
A few details worth knowing before you build anything on it:
- Expiry options are 30 days, 90 days, 180 days, or one year. Garmin emails you about a week before the key dies.
- The key is not a bearer token. Garmin Connect APIs use OAuth2, so you exchange the key at a token endpoint for an access token good for 24 hours.
- There are no refresh tokens. You just request a new access token from the same endpoint when the old one expires.
- You can revoke it any time from Garmin Connect, which kills the key and every token tied to it.
- Documentation lives on Garmin's Swagger pages and github.com/garmin, not in the Connect app.
That last point is the honest catch. Garmin is not adding a new screen to the Connect app or a no-code exporter. This is plumbing for people who can read an API reference. If your idea of a project is a personal dashboard, a spreadsheet pipeline, or feeding your training history into your own analysis, the door is now open. If you wanted a one-click export button, this is not it.
The three tiers, and where Garmin starts charging
The Personal tier covers your own activity and health data. DC Rainmaker, who checked the rollout with Garmin directly, confirms both Personal and the next tier up get JSON summaries and the full .FIT file for an activity.
Startup is aimed at groups supporting up to 1,000 users, and it adds the Courses and Training APIs. That is the piece Strava, Komoot and structured-workout platforms like TrainingPeaks use to push routes and planned sessions onto a watch, the sort of thing you feel immediately if you run a Garmin Forerunner and plan your week in advance. Approval at that level is meant to be close to instant.
Enterprise adds the Golf API, historical data backfill for new users, technical support, and unlimited users. This is the tier that costs money, and it is a real shift. DC Rainmaker reports an initial $1,000 entry fee that acts as credit toward a monthly active user bill, with the per-user rate negotiated per company. Existing partners get moved to Enterprise automatically and skip the entry fee, and nobody starts paying until April 1, 2027.
Garmin dropped a $5,000 entry fee for the Connect API back in 2019 and has kept it free since. Putting a per-user price on it now is the company saying it will no longer subsidize platform businesses built entirely on its data. It also lines Garmin up alongside Whoop, which already charges for deeper API access.
Nothing changes for Garmin Connect IQ, the app and watch-face platform. That stays free and untouched.
The part that still rubs developers wrong
Here is the tension in this rollout, and Garmin is not hiding it.
Both Personal and Startup get the full .FIT file, but Garmin strips out fields it considers proprietary before the file is handed to a third party. That is not new policy, it is just newly visible now that individuals are poking at the same pipes.
Runalyze reported the problem on October 6, and its changelog still carries the note that values no longer arrive over the Garmin connection. On the missing list: VO2 max estimates, recovery time, performance condition, training benefit and lactate threshold. Download the original .FIT manually from Garmin Connect and every one of those values is still sitting in the file.
Garmin's answer to Runalyze, dated March 16, is direct enough: everything documented in the public FIT SDK is still delivered, and undocumented messages and fields are removed before files go to third-party platforms. Garmin's position is that those fields were never part of the deal.
So the new Personal API fixes the access problem without fixing the completeness problem. You can now get your own data programmatically, and it will be the same trimmed version the commercial platforms get. Whether that matters depends on what you are building. Sleep, heart rate, pace and distance all arrive fine. The Garmin-specific training intelligence is the part that does not.
Garmin is behind COROS and Suunto on one thing
One more thing on where Garmin sits relative to its rivals right now. COROS rolled out MCP access free for all users, and Suunto announced its own version. DC Rainmaker's read is that Garmin's API is still the most feature-complete in the space, routes, structured workouts, completed activities, health data and women's health included. What COROS and Suunto beat Garmin on is the friction of getting in at all, which is exactly what this week was supposed to fix.
If you want to see how far Garmin has come, compare this to the state of the program in September, when there was no signup form and no reopening date. The approval mess that made people give up shows up in a different form too, in Garmin's Connect IQ review backlog.
Bottom Line
The Personal API is the most useful thing Garmin has shipped for data-minded owners in years, and it costs nothing. Eight seconds from login to API key, according to DC Rainmaker's own test.
Just go in knowing the shape of the deal. You get your own data, but not all of it, and Garmin is now officially a paid platform for anyone building on top of it at scale. If you were waiting for a reason to finally build the training dashboard you keep sketching out, the excuse is gone. A Garmin watch has been collecting the raw material for years. Now you can actually read it.
Sources: Garmin developer documentation (Garmin Connect Personal API FAQ and Personal API overview pages), DC Rainmaker, Gadgets & Wearables, Runalyze blog, Runalyze changelog, Garmin forums.
