Can you still get Garmin Connect API access in 2026? What changed for integrators
Garmin has paused new applications to the Garmin Connect Developer Program, which is the program that gives companies API access to Garmin health and activity data. Integrations that were already approved keep working. Garmin's API Brand Guidelines also require a visible "Garmin device model" attribution anywhere Garmin device data appears. That includes apps that get Garmin data from a third party and never connect to Garmin directly.
Is the Garmin Connect Developer Program accepting new applications?
No. The Garmin Connect Developer Program is not taking new applications, and Garmin has not said when it will start again. Several developers who applied in March and April 2026 say Garmin Connect Partner Services told them new API requests were paused while the program was being updated. The application form is gone from Garmin's developer site. The program page now just says "Stay tuned for more updates on the program." The5KRunnerGarmin Developers
The pause also affects applications that were submitted before it began. When one applicant escalated in May 2026, Garmin said it was redesigning and modernizing the API program and its processes. Garmin added that it could not process requests already in the queue and could not say when processing would resume. Garmin's public FAQ has not been updated to reflect any of this. It still says new applications are normally confirmed within two business days. The5KRunnerThe5KRunner
Does the pause affect existing Garmin integrations?
No. The pause applies only to new applicants. Garmin integrations that were already approved keep working. If your company already has production access, check your credentials and connection status directly. Don't rely on third-party reports for this. Momentum
Is Garmin Connect IQ affected by the pause?
No. Connect IQ is a separate Garmin program. It covers watch faces, data fields, widgets and apps that run on the device, and it is still open. The Garmin Connect Developer Program is different: it is the route cloud services use to receive Garmin health and activity data. A Connect IQ app does not give you that server-side data feed. Momentum
What are Garmin's attribution rules for API data?
Garmin requires you to credit Garmin wherever you show data that came from a Garmin device. Garmin introduced its API Brand Guidelines in July 2025, requiring Garmin attribution when Garmin data appears on third-party services. The guidelines set attribution requirements for five places: title-level displays, secondary screens, exported data, derived data and social media. The5KRunnerGarmin Developers
Four rules matter most for product teams:
Placement. The attribution must sit directly beneath or next to the main title or heading of the data view. Singletracks
Exports and images. When Garmin device data is exported into a visual asset, such as a social image, infographic, map or chart, the asset must carry a "Garmin [device model]" attribution. The attribution must be visible in every image. Garmin Developers
Expanded views. The attribution must also appear in every expanded view or subscreen. Garmin Developers
Device model. Developers are told to get the device model from the relevant API documentation. In practice, your data pipeline has to store which device recorded each data point. Garmin Developers
There is a narrow exemption in the developer agreement. The attribution rules do not apply to Garmin device data that comes only from the Health API and is used only in the defense, research or remote patient monitoring markets, or in other use cases Garmin has approved in writing. The exemption holds only if the data is not shown or shared with the licensee's own branding or a third party's. Before relying on it, read the current Garmin Connect Developer Program Agreement with your own counsel. Garmin
Do Garmin's attribution rules apply if you get Garmin data through a third party?
Yes. The rules follow the data, not the connection you received it through. Garmin's guidelines say derived data, including data that reaches you through fitness apps, devices, third-party APIs or manual inputs, must include a Garmin attribution. Strava has already written this into its own terms. Strava's updated API Agreement requires any application showing information derived from Garmin-sourced data to display Garmin attribution in the form Garmin's brand guidelines require. That requirement took effect on November 1, 2025. API brand guidelines +2
For product teams, this means switching data providers does not remove the obligation. If a screen in your app shows Garmin-recorded data, that screen needs the Garmin attribution.
What should product teams building on Garmin data do now?
Plan around the pause, and make your app meet the attribution rules now. Four concrete steps:
Keep Garmin-dependent features off your launch timeline unless you have direct Garmin approval in hand, or you are working through a partner that already has production access.
Audit every surface that shows wearable data: dashboards, detail screens, exports, shareable images, and AI-generated summaries built from that data.
Store the source device with each data point, so the correct "Garmin [device model]" label can be shown.
Keep developer approval and end-user consent separate in your design. They are different steps. Having one does not give you the other.
How ROOK supports companies integrating Garmin Connect data
ROOK already delivers Garmin Connect data through ROOK Connect. Companies integrate once with ROOK's API. They then receive Garmin data in the same standardized format ROOK uses for its other data sources. ROOK supports 72 data sources and more than 500 devices.
ROOK passes the source device model for each data point in its payloads, so customers can meet Garmin's attribution requirements. The customer's app is still responsible for displaying the attribution, as Garmin's guidelines require.
If Garmin data is on your roadmap, talk to us about your use case, the data types you need, and your attribution setup.
