Device IntegrationHealthcare Interoperability

Garmin API Integration Guide 2026: Health API and SDK

October 1, 202616 min read
Written by
Jitendra Choudhary
Jitendra Choudhary

CTO & Co-Founder

CTO & Co-Founder at Nirmitee.io. Architects healthcare integrations across FHIR, SMART on FHIR, ABDM and NHCX, writing from production experience taking hospital software from sandbox to go-live.

Garmin API Integration Guide 2026: Health API and SDK

Yes, you can integrate Garmin through the Garmin API, but not on the same day. You apply to the Garmin Connect Developer Program, and Garmin approves you before you get an evaluation environment. Business Starter is free, pushes data to your server and gives no history. Business Enterprise adds history, pull access, beat-to-beat intervals and unlimited users on commercial terms Garmin sets case by case. The rule that decides most healthcare projects is agreement section 5.6: you may not seek FDA marketing permission or take steps that could make the Garmin API or Garmin Connect a regulated product.

Want a team to build this for you? Our medical device integration services cover the vendor approval, the data pipeline and EHR delivery.

Garmin integration at a glance

QuestionAnswer
Official API?Yes. Garmin Connect Developer Program: Health, Activity, Women's Health, Training, Courses and Golf APIs.
Cost to the developerAgreement 10.1: no license fees today, 30 days notice before charging. Garmin may charge for request volume over the limits (10.2). Enterprise terms are "tailored".
Does the end user need a subscription or device?A Garmin device synced to Garmin Connect. No user subscription is mentioned in our sources.
Same-day start?No. You apply first. Approval time not published.
Who approves scale-up?Garmin. Starter has "limited user capacity". Enterprise (unlimited users) is by request.
HIPAA / BAANot published for the cloud API. Garmin describes its Standard Health SDK as HIPAA-compliant.
Raw or summary data?Cloud API: summaries, including epoch summaries. Beat-to-beat on Enterprise. Real-time raw streams only through the Health SDK.
First buildAbout 4 weeks after approval (our estimate). Approval and Enterprise terms depend on Garmin.

Integration strategies

RouteOwn mobile app?Own server?Vendor approval or contract?SDK?LatencySupported dataNot supportedBest for
Business Starter (cloud, push)No. A web page for consent is enough.Yes, to receive pushesYes. Application and Developer Program Agreement.NoAfter the user syncs to Garmin Connect. Delay not published.Health, Activity, Training, Courses. Women's Health per the overview table. The Women's Health API page marks only ping/pull, multi-project and backfill as Enterprise only.History, backfill, pull, beat-to-beat, GolfPilots and wellness products that only need data from the day users connect
Business Enterprise (cloud, push or ping/pull)NoYesYes. Request through the portal, tailored commercial terms.NoSame as StarterAll Starter data plus 1 month or more of history, backfill, enhanced beat-to-beat interval, Golf, supportReal-time streamsRPM, population health, trials, any scale
Garmin Health SDK (Standard or Companion)YesStandard SDK: yes, data lands in your systemsYes. Enterprise partners only. Commercial use needs a license fee or minimum device order.YesReal timeHeart rate, beat-to-beat, pulse ox, accelerometer streamsNot publishedDevice-provisioned clinical programs and studies that need raw data
Activity API .FIT filesNoYesSame as cloud tierNoPer activityActivity files in .FIT formatAll-day health dataSports and training apps
Apple Health / Health ConnectGarmin Connect writes to both and reads nothing back. Health Connect writing started in July 2025. Data includes steps, distance, calories, heart rate, sleep, weight, body fat, floors and workouts. Body Battery, stress, training load, HRV status and GPS tracks are not written. Garmin does not publish this in its developer docs, and our type list comes from third-party reports, so test it before you plan on it.
Aggregators, checked 10 November 2026Terra, Junction, Thryve and ROOK list Garmin as a cloud API source. Sahha has it in public beta, sandbox only. Spike lists it with no route stated. Validic coverage is not published. Pricing is not published. Garmin terms still apply.
Personal tierYour own data only. Not for a product.

For a wellness or coaching product, start on Business Starter. It is free, and push delivery is enough if you only need data from the day a user connects. For a healthcare buyer, plan for Enterprise from the start, because most clinical programs need history, backfill after outages and pull access to repair gaps. If you need raw sensor streams or you hand out the devices yourself, ask Garmin about the Health SDK.

Build it yourself, use an aggregator, or work with a partner

QuestionBuild in-houseWearable aggregatorBuild with a partner (Nirmitee)
Whose Garmin developer account?YoursDepends on the aggregator. Garmin does not publish how aggregator access works.Yours. We build it in your account.
Agreement riskYour counsel reads sections 5.6 and 9The aggregator's own Garmin terms apply on top of yoursYour counsel reads it. We design storage and retention around the answer.
Push receiver, token refresh, deregistrationYou build and run themThe aggregator runs themWe build them, then hand them to you or run them
Data modelGarmin's own summariesThe aggregator's schemaFHIR Observations for your EHR or remote monitoring stack
Other devices laterOne new build per deviceMany devices through one APISame pattern reused across devices
Time to first real userGarmin's FAQ says a typical integration takes 1 to 4 weeks after approvalDepends on the aggregator's onboardingAbout 4 weeks after approval in our estimate, see the Delivery timeline
Cost shapeEngineering time. No Garmin license fee today (agreement 10.1).Aggregator fee. Pricing is not published.Project fee, scoped after a call
Every way to get Garmin data, and what each one needs.

What data you can get

Garmin publishes the data categories. The exact endpoint list and summary schemas sit in the portal specification, which is not public.

DataGranularityHistory windowPush or pull
Heart rate (all day)Summaries and epoch summariesStarter: none. Enterprise: 1 month or more.Starter push. Enterprise push or ping/pull.
Steps, caloriesDaily and epoch summariesSameSame
SleepSleep summarySameSame
Stress (detailed)SummarySameSame
RespirationSummarySameSame
Pulse oxSummarySameSame
Body compositionPer measurementSameSame
Beat-to-beat interval (enhanced)Interval levelEnterprise onlyEnterprise only
ActivitiesPer activity, .FIT files availableSame tier rulesSame tier rules
Women's HealthNot publishedNot publishedStarter push. Enterprise push or ping/pull.
Training, CoursesNot publishedNot publishedStarter and Enterprise
GolfNot publishedNot publishedEnterprise only
Real-time HR, beat-to-beat, pulse ox, accelerometerRaw streamsn/aHealth SDK only

All of it is available only after the user consents and syncs the device to Garmin Connect.

What is inside a Garmin Health API summary

Garmin does not publish field names or a sample payload outside the portal. Its public pages do list what the Health API covers, read 11 Nov 2026.

ItemWhat Garmin publishes
MetricsSteps, intensity minutes, sleep, calories, heart rate, stress, pulse ox, Body Battery, body composition, respiration and blood pressure. Enhanced beat-to-beat interval is Enterprise only.
Summary typesDaily summaries plus detailed stress, pulse ox and epoch summaries for all-day activity
Finest heart rate"Second-level HR during activities"
Activity filesJSON summaries, or .FIT, GPX and .TCX files for full activity details
Women's HealthMenstrual cycle tracking and pregnancy tracking, including schedules and phase details
Subscriptions"Only subscribe to the data you need." Sample data and auto-verification before production are in the developer web tools.
User keyEach user has one API User ID that stays the same across tokens and across your programs. Push and ping notifications carry it.
Field names, units, epoch lengthNot published

Training and Courses work the other way. They send workouts, training plans and courses from your app to Garmin Connect, and the user's device picks them up on its next sync.

What you cannot get

  • On Starter: any history before the user connected, any backfill, beat-to-beat intervals, ping/pull access, Golf.
  • Raw sensor streams through the cloud API. Those come only from the Health SDK.
  • ECG. Not listed in our sources.
  • A public endpoint list or schema. You see it only inside the portal after approval.
  • Published latency or rate limits.
  • Data from users who have not synced their device recently. The cloud API only sees what reached Garmin Connect.

How to get access

  1. Apply through Garmin's "REQUEST NOW" form on the developer program pages. Garmin approves. Criteria and wait time not published. Third-party guides quote days, but that is not a Garmin source.
  2. Accept the Garmin Connect Developer Program Agreement.
  3. After approval, create an app with Starter access. Garmin gives you an evaluation environment to test the Health API.
  4. Build and test with real users within Starter's "limited user capacity". A search summary quoted 1,000 connected users, which we could not confirm on a Garmin page.
  5. When you need history, pull access, beat-to-beat or more users, request Enterprise through the Garmin Developer Portal. Garmin sets commercial terms. Timeline not published.
  6. For the Health SDK, become an Enterprise partner, evaluate for free, then agree a license fee or minimum device order for commercial use.

From zero to your first Garmin data in four steps

  1. Get approved. Request access to the Garmin Connect Developer Program. After approval you get the Garmin Developer Portal, the technical docs and an evaluation environment. Create an app with Starter access and note the client ID and client secret.
  2. Connect a user with OAuth2 PKCE. Make a code verifier of 43 to 128 characters and send the user to https://connect.garmin.com/oauth2Confirm with code_challenge_method=S256. Swap the code for tokens at https://connectapi.garmin.com/di-oauth2-service/oauth/token on your server. Garmin's OAuth2 tool at apis.garmin.com/tools/oauth2/authorizeUser shows the flow.
  3. Check who connected and what they shared. Fetch the user ID from /wellness-api/rest/user/id, then the permissions the user granted.
    curl --request GET \
      --url https://apis.garmin.com/wellness-api/rest/user/permissions \
      --header 'Authorization: Bearer <access_token>'
  4. Receive pushes. Register your push endpoint in the portal. Data arrives after the user syncs the device to Garmin Connect, and each notification carries the user ID. Refresh the access token before it expires. Garmin recommends taking 600 seconds or more off expires_in.

Terms you must know

From the Garmin Connect Developer Program Agreement (PDF file dated 4 Oct 2023).

  • FDA compliance, 5.1(i) and (j). You must follow all FDA laws and market your product only for its cleared or approved intended use. Healthcare: your regulatory claims must match your clearance. Wellness: avoid medical claims entirely.
  • No regulatory filings that pull Garmin in, 5.6. You "will not seek any regulatory marketing permissions or make any determinations" that could make the API, Garmin Connect or any Garmin product a regulated product. Healthcare: an FDA-cleared RPM product or software as a medical device built on Garmin data needs a read by regulatory counsel and a conversation with Garmin first. Wellness: little effect, as long as you make no medical claims.
  • No credit, insurance or employment decisions (FCRA section 604 clause, near 5.4). Healthcare and payers: you cannot use Garmin data to set insurance eligibility or premiums. Employer programs: you cannot use it in hiring or employment decisions. Rewards for activity need a legal read.
  • Breach notice, 5.1(h). Report breaches to Garmin within 24 hours. Both readers: add Garmin to your incident runbook.
  • PHI, HIPAA and BAA. Not published for the cloud API. The Standard Health SDK is described as HIPAA-compliant. Healthcare: ask Garmin in writing before patient data flows.
  • Termination, 9. Garmin may end the agreement on 30 days notice. On termination you must destroy copies of API data. Healthcare: plan how a clinical record survives this clause. Wellness: tell users what happens to their history.
  • Fees, 10.1 and 10.2. Free today, 30 days notice before charging, possible fees for volume over the Application Requirements.
  • Data transfers. The agreement includes Standard Contractual Clauses. Region choice is not published.
  • AI training, data selling, display and branding, competing products. Not covered in our research of the agreement. Read the full PDF before you sign.

Cost and payment terms

  • Developer Program: no license fees today (10.1). Garmin's Japanese pages also say access is free for approved business developers (read via a search summary only).
  • Volume over the limits: Garmin may charge (10.2). Limits are in the Application Requirements, not public.
  • Enterprise: "commercial terms are tailored based on business and technical requirements". No price published.
  • Health SDK: free to evaluate. Commercial use needs a "License Fee or Minimum Device Order Quantity". Amounts not published.
  • End user: buys a Garmin device. No subscription is mentioned in our sources.
  • Aggregators: pricing not published.

Use cases

Garmin data from consent to the EHR.

Remote patient monitoring after discharge

The care team enrolls the patient and the patient approves Garmin access on a consent page. Each time the watch syncs, Garmin pushes daily, sleep, pulse ox and respiration summaries to your server. You map heart rate, SpO2 and respiration to FHIR Observations and write them to the EHR, and a nurse dashboard flags out-of-range trends.

  • No sync, no data. A patient who never opens Garmin Connect sends nothing. Fix: a "last synced" alert after a set number of days.
  • Missed push on Starter. Your endpoint was down and Starter has no backfill. Fix: run clinical programs on Enterprise so you can pull and backfill.
  • Regulatory scope. If your RPM workflow depends on FDA clearance, section 5.6 may block it. Fix: review 5.6 with regulatory counsel and Garmin before go-live.

Clinical trial with HRV endpoints

Sites hand participants Garmin devices. Participants link Garmin in the study app. Enterprise pushes summaries and beat-to-beat intervals, and you pull history to cover gaps. Data lands in the study database with participant IDs, not names.

  • Beat-to-beat needs Enterprise. Fix: agree Enterprise terms before the protocol is final.
  • Termination clause requires destroying copies. Fix: agree retention for trial records with Garmin in writing.
  • Need for raw streams. Fix: evaluate the Health SDK, which also means a license fee or minimum device order.

Employer wellness program

An employee connects Garmin in your app. Starter pushes steps, sleep and stress summaries. Your server updates challenge scores and the employee's screen.

  • Employment decisions clause. Fix: keep data out of HR systems, state this in your privacy notice.
  • Starter user cap. Fix: request Enterprise before a company-wide rollout.

Population health or payer engagement

Members link Garmin in the plan's app. Enterprise pull gives a month or more of history at enrollment, so the program sees a baseline from day one. Aggregated activity trends feed outreach lists.

  • Insurance eligibility ban. Fix: never use Garmin data in underwriting or eligibility. Keep it in engagement only.
  • PHI. Fix: written answer from Garmin on HIPAA before launch.

Sleep or recovery app

A user connects Garmin from your app's settings screen through a web consent page. After each morning sync, Starter pushes the sleep summary, respiration and stress summaries to your server. Your app shows last night's sleep and a recovery trend.

  • The user did not sync. Nothing arrives until the watch syncs to Garmin Connect. Fix: show "last synced" on screen and send a reminder.
  • Empty first week on Starter. There is no history before the user connected. Fix: say so in onboarding, or use Enterprise to load a month or more of history.
  • Sleep stages and scoring fields are not published. Fix: read the portal schema before you design screens.

Training and coaching app

An athlete connects Garmin. Each activity arrives by push, and you fetch the .FIT file for detailed analysis. Training and Courses APIs are also in the program. Their schemas are in the portal.

  • No history on Starter, so new users start with an empty screen. Fix: set expectations in onboarding, or move to Enterprise for backfill.
  • Repeat pushes for the same activity or day. Fix: overwrite by user and summary period instead of appending. Confirm the record keys in the portal spec.

Garmin data in an EHR or remote monitoring program

Most healthcare teams want Garmin readings next to clinical data, not in a separate app. The usual pattern is to turn each reading into a FHIR Observation, the standard record for a measurement, and send it to the EHR or the remote monitoring platform. Read agreement sections 5.6 and 9 first, because they decide what you may claim and what you must delete.

Garmin valueFHIR ObservationCode
Heart rateHeart rate, beats per minuteLOINC 8867-4
RespirationRespiratory rateLOINC 9279-1
Pulse oxOxygen saturation, percentLOINC 2708-6, plus 59408-5 for pulse oximetry
Blood pressureBlood pressure panelLOINC 85354-9, with 8480-6 systolic and 8462-4 diastolic
StepsStep countLOINC 55423-8
SleepSleep durationLOINC 93832-4
Body compositionBody weight, BMILOINC 29463-7, 39156-5
Stress, Body Battery, beat-to-beat intervalsDevice-specific ObservationYour own code system. These are Garmin's own scores or raw intervals, so no standard code fits exactly.

Store the Garmin API User ID and the summary period on each Observation, so a repeat push for the same day replaces the old record instead of adding a second one. If your app has its own Disconnect or Delete My Account button, the PKCE spec says you must call DELETE /wellness-api/rest/user/registration.

Known blockers and gotchas

  • Two auth stories. Garmin's OAuth2 PKCE spec is dated 11 Jun 2025. A now-removed Garmin FAQ said all APIs use OAuth 1.0a. Garmin's Program FAQ, read 11 Nov 2026, now says all Developer Program APIs use OAuth 2.0, so build on OAuth2 PKCE. The OAuth 1.0a sunset date is not published.
  • Token lifetime conflict. The PKCE PDF shows expires_in 86400 (24 hours) and a refresh token of about 90 days, but its text says access tokens expire after three months. Test in the evaluation environment and code for the shorter one.
  • Rotating refresh tokens. Each refresh returns a new refresh token. Store it every time.
  • Permissions. Garmin publishes a user permissions endpoint. Call it before you expect a data type. The PKCE spec lists the permission values ACTIVITY_EXPORT, WORKOUT_IMPORT, HEALTH_EXPORT, COURSE_IMPORT and MCT_EXPORT. Changes after consent arrive on the User_Permission webhook.
  • Women's Health tier confusion. The overview table lists it for Starter and Enterprise. The Women's Health API page, read 11 Nov 2026, marks only ping/pull, multi-project and backfill as Enterprise only.
  • Hidden limits. Rate limits sit in the Application Requirements. Ask for them during approval.
  • No Starter backfill. Any receiver downtime means lost data. Monitor your push endpoint like a production service.
  • Deregistration. Plan for users who disconnect. Handle deregistration so you stop expecting data and clean up. The exact event is in the portal spec.

Delivery timeline

Our estimate. Steps marked "vendor" depend on Garmin.

WeekWorkDepends on vendor?
0Apply, accept agreement, wait for approvalVendor, no published wait
1 to 2OAuth2 PKCE, permission check, push receiver in the evaluation environmentNo
3 to 4FHIR mapping, dedupe updates, deregistration handling, sync-gap alertsNo
4 onwardProduction access, Enterprise upgrade, backfillVendor, contract step
If raw data neededHealth SDK evaluation and licenseVendor

Questions to ask Garmin before you sign

  1. How long does approval take, and what do you look for?
  2. What is Starter's exact user limit?
  3. What does Enterprise cost for our user count and data types?
  4. How does section 5.6 apply to our FDA-cleared workflow?
  5. Will you sign a BAA for the cloud API?
  6. Can we keep data in the EHR or study database after termination under section 9?
  7. Are we on OAuth2 PKCE or OAuth 1.0a, and what is the real access token lifetime?
  8. What are our rate limits under the Application Requirements?

Other device integration guides

Garmin is often one device among several. Each guide below uses the same layout, so you can compare access, data and terms side by side. For the full service, see medical device integration.

Ready to build with Garmin?

We build device integrations into healthcare and wellness products, including FHIR mapping and EHR delivery. We have no partnership with Garmin. Tell us your device, your users and your target date, and we will send back the route, the vendor approvals you need and a build plan. Book a call about your device integration.

For whoever builds this

  • OAuth2 PKCE (Garmin PDF, 11 Jun 2025). Authorize: https://connect.garmin.com/oauth2Confirm with code_challenge_method S256. Token: https://connectapi.garmin.com/di-oauth2-service/oauth/token with client secret and code_verifier.
  • Sample token response: expires_in 86400, refresh_token_expires_in 7775998. New refresh token on each refresh. PDF text says three months for access tokens. Verify.
  • User permissions: https://apis.garmin.com/wellness-api/rest/user/permissions. Permission values: ACTIVITY_EXPORT, WORKOUT_IMPORT, HEALTH_EXPORT, COURSE_IMPORT, MCT_EXPORT. The token scope string is fixed and cannot be changed.
  • Endpoints, schemas and rate limits: in the portal spec after approval.
  • Format: JSON over REST. Activity files in .FIT.
  • FHIR (LOINC from the FHIR R4 vital signs profile): heart rate 8867-4, respiratory rate 9279-1, SpO2 2708-6, body weight 29463-7, BMI 39156-5.
  • Checked on the NLM LOINC search 11 Nov 2026: steps 55423-8, sleep duration 93832-4, blood pressure panel 85354-9 (systolic 8480-6, diastolic 8462-4), pulse oximetry 59408-5, body fat 41982-0. Stress, Body Battery and beat-to-beat have no exact standard code.
  • Version notes: tier model Personal, Business Starter, Business Enterprise. Launch date of the new program not confirmed (Garmin blog returned 403).

Sources

All read 10 Nov 2026.

  • Android Police on Garmin and Health Connect, https://www.androidpolice.com/garmin-data-sharing-google-health-connect-details/, read 10 November 2026.
  • Terra supported integrations, https://docs.tryterra.co/reference/health-and-fitness-api/supported-integrations, read 10 November 2026.
  • Junction providers list, https://docs.junction.com/wearables/providers/introduction, read 10 November 2026.
  • Thryve data sources overview, https://docs.thryve.health/thryve-data-sources/overview, read 10 November 2026.
  • ROOK data sources, https://docs.tryrook.io, read 10 November 2026.
  • Sahha integrations, https://www.sahha.ai/docs/connect/integrations.md, read 10 November 2026.
  • Spike integrations, https://www.spikeapi.com/integrations, read 10 November 2026.
  • Validic supported devices and restricted vendor list, https://www.validic.com/features/supported-devices/, read 10 November 2026.
  • https://developer.garmin.com/gc-developer-program/overview/
  • https://developer.garmin.com/gc-developer-program/enterprise/health-api/
  • https://developer.garmin.com/gc-developer-program/enterprise/womens-health-api/ (search summary)
  • https://developer.garmin.com/health-sdk/overview/
  • https://developerportal.garmin.com/sites/default/files/OAuth2PKCE.pdf
  • https://developerportal.garmin.com/sites/default/files/Garmin%20Connect%20Developer%20Program%20Agreement.pdf
  • https://developer.garmin.com/gc-developer-program/health-api-japanese/ (search summary)
  • https://hl7.org/fhir/R4/observation-vitalsigns.html
  • https://developer.garmin.com/gc-developer-program/enterprise/program-faq/, read 11 November 2026.
  • https://developer.garmin.com/gc-developer-program/enterprise/activity-api/, read 11 November 2026.
  • https://developer.garmin.com/gc-developer-program/enterprise/training-api/ and /courses-api/, read 11 November 2026.
  • https://developer.garmin.com/connect-iq/overview/, read 11 November 2026.
  • LOINC codes checked on https://clinicaltables.nlm.nih.gov/, 11 November 2026.

Ready to scale?

Talk to our healthcare engineering team about building, integrating, and shipping faster.

Frequently Asked Questions

Does Garmin have an API for health data?

Yes. The Garmin Connect Developer Program offers Health, Activity, Women's Health, Training, Courses and Golf APIs. You apply and Garmin approves you before you get an evaluation environment.

Is the Garmin Health API free?

The Developer Program Agreement (section 10.1) says no license fees are due today, with 30 days notice before Garmin charges. Garmin may charge for request volume over its limits. Enterprise commercial terms are tailored per business and not published.

What is the difference between Garmin Business Starter and Business Enterprise?

Starter is push only, has no historical data and has limited user capacity. Enterprise adds push or ping/pull, history of one month or more, backfill, unlimited users, enhanced beat-to-beat intervals, Golf and support.

Can I get historical Garmin data for a new user?

Only on Business Enterprise, which offers one month or more of history and backfill. Starter gives no data from before the user connected.

Can I get raw heart rate or accelerometer data from Garmin?

Not through the cloud API. Real-time heart rate, beat-to-beat, pulse ox and accelerometer streams come from the Garmin Health SDK, which is for Enterprise partners and needs a license fee or minimum device order for commercial use.

Is the Garmin Health API HIPAA compliant?

Garmin does not publish a HIPAA statement or BAA for the cloud API. Garmin describes its Standard Health SDK as HIPAA-compliant. Ask Garmin in writing before patient data flows.

Can I use Garmin data in an FDA-cleared remote patient monitoring product?

Read section 5.6 of the agreement first. It says you will not seek regulatory marketing permissions or make determinations that could make the API, Garmin Connect or any Garmin product a regulated product. Review it with regulatory counsel and Garmin before you build.

Can insurers or employers use Garmin data for decisions?

No. The agreement bans using the data for credit, insurance eligibility or employment decisions, citing FCRA section 604.

How long does Garmin developer approval take?

Garmin does not publish approval criteria or wait times. Third-party guides quote days, but that is not a Garmin source.

Which OAuth does the Garmin API use?

Garmin publishes an OAuth2 PKCE spec dated June 2025. An older Garmin FAQ said OAuth 1.0a, and no sunset date for 1.0a is published. Confirm with Garmin which one your app uses.

What happens to Garmin data if the agreement ends?

Garmin may terminate on 30 days notice, and you must then destroy copies of API data (section 9). Agree retention for clinical or study records with Garmin in writing.

Which permissions can a Garmin user grant?

Garmin's PKCE spec lists ACTIVITY_EXPORT, WORKOUT_IMPORT, HEALTH_EXPORT, COURSE_IMPORT and MCT_EXPORT. A user can opt in to fewer than your app asks for, so call the user permissions endpoint after consent. Later changes arrive on the User_Permission webhook.

How long do Garmin access tokens last?

The spec's sample response shows expires_in 86400, which is 24 hours, and a refresh token of 7,775,998 seconds, about 90 days. Its text also says three months for access tokens. Code for 24 hours, take 600 seconds or more off as Garmin recommends, and store the new refresh token from every refresh.

Is the Garmin API push or pull?

Starter is push only. Enterprise adds ping/pull. The Personal tier, for your own data, is pull only. In every case data appears only after the user syncs the device to Garmin Connect.

What happens when a user disconnects my app?

If the user removes consent in Garmin Connect, Garmin handles it. If your own app has a Disconnect or Delete My Account option, the PKCE spec says you must call DELETE /wellness-api/rest/user/registration so Garmin stops sharing that user's data.

Is Connect IQ the same as the Garmin Health API?

No. Garmin's FAQ says they are different programs and one does not need the other. Connect IQ is a free SDK for watch faces, data fields, widgets and device apps on the watch. The latest version listed on 11 Nov 2026 is Connect IQ 9.3.0. The Health API sends summaries from Garmin Connect to your server.

Are rate limits for the Garmin API published?

No. The agreement points to the Application Requirements, which are inside the portal. Garmin may charge for request volume over those limits (section 10.2), so ask for the numbers during approval.
Share