How to Integrate the Garmin API (2026)

Garmin is not a sign-up-and-ship API. Everything below comes from Garmin's public Connect Developer Program pages as read on October 22, 2026, after Garmin reorganised them into Business and Personal sections; the detailed API reference is only available to approved developers, so where a value lives behind that login this guide says so instead of guessing. The Garmin API overview tracks the access gate alongside every page on this site that covers Garmin.

Two naming traps first. Connect IQ, Garmin's platform and free SDK for apps that run on the watch itself, is a different program from the cloud APIs covered here, and Garmin says one does not require the other; Connect IQ vs the Health and Activity APIs explains the split. And if all you need is your own account's data rather than other users', Garmin now has a Personal API with a key you create yourself; see Garmin API for personal use.

Access and approval#

Garmin's FAQ says the program "supports a broad range of organizations, from individual developers and startups to companies operating at significant scale". Access comes in two levels:

The path the FAQ describes is short: request access, and once your request has been approved you get the Garmin Developer Portal and "can get started on your integration right away". "All detailed technical information and documentation is available within the Garmin Developer Portal." Garmin says "A typical integration takes between 1 and 4 weeks." The overview says to create an app with Starter Access and request Enterprise Access through the Developer Portal as your needs grow. The Health API page adds an evaluation environment for testing after approval.

Garmin no longer states how long the review takes. Until October 2026 its FAQ promised a decision within two business days and an integration call; neither is on the current pages.

The five APIs#

Garmin says you can use any or all of the program's APIs in a single application:

Enterprise Access adds a sixth, the Golf API, on the overview's plan card; it has no page of its own in the program menu. The Health API page positions the API for corporate wellness, population health and patient monitoring. Garmin says new devices are supported automatically and that it tries to add new data types as devices launch, but that "it's not always possible to offer every metric".

Garmin's Activity API page no longer gives a count of activity types. Earlier versions of this guide quoted the overview's "over 30 activity types"; that sentence is not on the reorganised pages.

Auth and scopes#

Garmin's FAQ answers the auth question in one line: "All APIs in the Developer Program use OAUTH 2.0." The authorization and token endpoints, scopes and token lifetimes are in the documentation approved developers receive, not on Garmin's public pages, so this guide does not reproduce them. Take those values from the Developer Portal once you have access.

Getting data: push or ping/pull#

Garmin's API pages describe the delivery model, and mark some of it with an asterisk that reads "Supported with Enterprise Access only":

• Push, or ping/pull on Enterprise. The Health and Women's Health pages offer "Push or *Ping/Pull Architecture"; the overview lists Starter delivery as push only.
• Customized data feeds. "Only subscribe to the data you need."
• Multi-project support (Enterprise only). Each app is created and configured independently.
• Developer web tools. On-boarding, sample data, backfill of user data (Enterprise only) and auto-verification of your integration before production.

Data arrives on the user's schedule: after initial consent, users sync their device with Garmin Connect, "at which point it is accessible via the API". The Health API delivers JSON summaries of what the user uploaded, including detailed stress, Pulse Ox and epoch summaries for all-day activity. On Starter, plan an endpoint Garmin can push to and an ingestion path that tolerates data arriving whenever a user happens to sync, with no historical backfill to lean on.

For the reverse direction, the Training and Courses APIs publish to the user's Garmin Connect account after they consent, and Garmin Connect handles the device side: the user syncs and the workout or course lands on the watch or cycling computer.

Rate limits#

Garmin's public pages publish no request limits. The overview gives Starter a "Limited" user capacity and Enterprise an "Unlimited" one without saying what the Starter limit is; ask for it in writing.

Fees#

Garmin's pages, read on October 22, 2026, state no price for Starter Access and say Enterprise options and commercial terms "are tailored based on business and technical requirements". The FAQ sentence this guide used to quote, that there were no licensing or maintenance fees with licence fees for some metrics, is gone. If you plan to supply Garmin wearables to your users, the FAQ now says to request the program and use Garmin's inquiry form. The Garmin API pricing page breaks this down.

What changed recently#

Garmin publishes no public changelog for the program. Comparing its pages on October 22, 2026 with this guide's October 17 version:

• Starter and Enterprise Access. The program now has two levels, with ping/pull delivery, multi-project support, backfill, historical data and enhanced beat-to-beat interval on the Enterprise side.
• A Personal API. Individuals can create their own key for their own data; the business FAQ sends personal-use questions there.
• New addresses. The program FAQ and the five API pages moved under /gc-developer-program/enterprise/; the old addresses return 404.
• Gone from the pages: the "Stay tuned for more updates on the program" banner, the business-use-only and no-licensing-fee sentence, the two-business-day decision, the integration call and the "over 30 activity types" line.
• OAuth 2.0 across the board, still.

Gotchas and production notes#

• Starter is push only, without history. If you need ping/pull, backfill or more than limited user capacity, you are planning for Enterprise and its tailored terms.
• Personal API is not a shortcut for products. Garmin says it is not intended for commercial applications serving multiple end users.
• Sync drives freshness. Nothing reaches the API until the user syncs their device with Garmin Connect.
• Consider an aggregator if approval stalls. A wearable-data aggregator that already holds Garmin access can cover it through one integration; compare that path in wearable data APIs and see how Garmin stacks up against self-serve options in Fitbit API vs Garmin API.