Understand the process and current status for obtaining Garmin Health/Activity API access
domain: developer.garmin.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Review the Health API (all-day metrics: heart rate, sleep, steps) and Activity API (30+ activity types) product pages to confirm fit for your use case
Submit a partner application describing your company, use case, and data-handling practices — there is no self-serve credential for full server-side health data access
If approved, use the provisioned evaluation environment and expect an integration call before full Developer Portal access is granted
Build against Garmin's push-notification model (Garmin pushes data to your registered endpoint) rather than a pull/polling model
Verify current program availability before planning a timeline — Garmin has publicly paused/suspended new developer program sign-ups, with no announced resumption date
Known gotchas
The Garmin Connect Developer Program has been reported on hold and not accepting new applicants — confirm current status directly on developer.garmin.com before committing to a timeline
This is a partner-approval program, not a self-serve API — approval can take days to weeks and is not guaranteed
Health API and Activity API are separate products with separate scopes; consumer vs. research/clinical use cases go through different application pathways
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?