--- title: "Garmin API for Personal Use: Garmin's Official Personal API" canonical: "https://aifitnessapi.com/fix/garmin-api-personal-use" cluster: "Troubleshooting" primary_query: "garmin api for personal use" last_reviewed: "2026-10-22" description: "Garmin now has a Personal API for your own Garmin Connect data: a key you create, 24-hour tokens, not for multi-user apps. Setup, limits and alternatives." publisher: "AIFitnessAPI — independent, not sponsored" cite_as: "\"Garmin API for Personal Use: Garmin's Official Personal API\", AIFitnessAPI, https://aifitnessapi.com/fix/garmin-api-personal-use" --- # Garmin API for Personal Use: Garmin's Official Personal API > Yes. Garmin's developer site now documents an official Garmin Connect Personal API, which Garmin says "is available for personal use": you create an API key on Garmin Connect Web, exchange it for an access token that lasts 24 hours, and read your own activity, health and women's health data. Garmin says it is not intended for commercial applications serving multiple end users; those go through its Connect Developer Program, now split into Starter and Enterprise access. Read on October 22, 2026, this replaces the old answer that Garmin's program was business-only, and it turns unofficial clients like garminconnect into a fallback rather than the only route. - Canonical: https://aifitnessapi.com/fix/garmin-api-personal-use - Last reviewed: 2026-10-22 - Publisher: AIFitnessAPI (https://aifitnessapi.com) — independent, not sponsored - Cite as: "Garmin API for Personal Use: Garmin's Official Personal API", AIFitnessAPI, https://aifitnessapi.com/fix/garmin-api-personal-use --- Until this month the honest answer to "does Garmin have an API for personal use" was no: this site's [Garmin approval guide](/fix/garmin-api-approval) quoted Garmin's program FAQ, read on October 17, 2026, saying the program was only for business use. Garmin's developer site has since been reorganised: the program pages now sit under a Business section, and a new Personal section documents an official **Garmin Connect Personal API**. Garmin gives no launch date: the Personal section was absent from the program pages a source-snapshot run read on October 17, 2026, and present when another run read them on October 22, 2026. This page is built from that October 22 read. ## What Garmin now says about personal use Garmin's Personal API FAQ opens with the answer: "The Garmin Connect Personal API is available for personal use and is the quickest way to gain access to your data for use in personal applications." It describes the API as a way for Garmin customers "to securely access their own Garmin Connect data using an API", aimed at "developers, hobbyists, data enthusiasts, and individuals who want to build personal applications using their own Garmin data." The business side points the same way. Garmin's Connect Developer Program FAQ, which now sits under the Business section, asks "What if I would like API access to my data for personal use?" and answers: "Please visit the Garmin Connect Personal API for more information." ## Personal API or Developer Program? The line Garmin draws is whose data you read and who uses your app. | | Garmin Connect Personal API | Garmin Connect Developer Program | |---|---|---| | Built for | "individual Garmin users who want programmatic access to their own data" | "organizations building integrations for multiple users" | | Commercial apps | "not intended for commercial applications serving multiple end users" | Includes "commercial business APIs and enterprise options" | | Credential | A self-generated API key, exchanged for an access token | OAuth 2.0 for every program API | | Getting in | Create the key yourself on Garmin Connect Web | Request access; once approved you get the Garmin Developer Portal | | Data Garmin lists | Activity data (JSON and .FIT), health data (JSON), women's health data (JSON) | Health, Activity, Women's Health, Training and Courses APIs | | Delivery | Pull only | Push; ping/pull is marked "Supported with Enterprise Access only" | The Business FAQ describes two levels. Starter Access means "Developers can gain immediate access and launch with Garmin, with access to core data and tools", and Enterprise Access is "For companies operating at scale". If you are building for other people, that is your route, and the [Garmin approval guide](/fix/garmin-api-approval) covers it. ## How to get a Garmin Personal API key Garmin's steps, from its Personal API page: 1. Go to the Personal API Key page while logged in to your Garmin Connect Web account. 2. Select **Create Key**, then read and accept the Terms and Conditions. 3. Choose an expiration period: Garmin's FAQ lists 30 days, 90 days, 180 days or one year. 4. Copy the key. Garmin says it "will only be displayed once", so store it like a password. If you lose it, you delete it and generate a new one. 5. Exchange the key for an access token. Garmin says the key "cannot be used directly"; you call the token endpoint with the key in the Authorization header: ```bash curl -X POST 'https://personal.connectapi.garmin.com/personalapitoken-service/personal-api/personal-api-key/token' \ -H 'Authorization: ApiKey [your-api-key]' ``` The response is an OAuth 2 access token for supported Garmin Connect APIs. Garmin says access tokens "are valid for 24 hours or until the Personal API key expires, whichever occurs first", and that refresh tokens are not supported: you call the same endpoint again for a new token. Garmin emails you about a week before the key expires, and deleting the key on Garmin Connect Web makes the key and its access tokens unusable. ## What we could not verify - **The endpoint list.** Garmin points developers to its Personal API Swagger documentation, but that page builds itself in the browser and our snapshot captured no endpoints. Check it yourself before you plan a project around a specific metric. - **The terms.** You accept Terms and Conditions when you create a key, and they sit behind a Garmin Connect login, so we have not read them. Rate limits and permitted uses beyond Garmin's FAQ wording are therefore not stated here. - **The old FAQ.** The program FAQ address this site cited on October 17 no longer loads; its replacement under the Business section no longer contains the "only for business use" sentence other pages here quote. ## The unofficial clients: still an option, no longer the only one Before the Personal API, people reading their own Garmin data used unofficial Python clients that sign in with a Garmin username and password. - **garminconnect** (`cyberjunky/python-garminconnect`). Its README says: "This is an unofficial client for Garmin's web services". It logs in through the mobile sign-in flow Garmin's own apps use, stores tokens in `~/.garminconnect/garmin_tokens.json`, and warns that its write methods "can change Garmin account data". Its `login()` tries several strategies, "each with and without TLS impersonation". Details on [the garminconnect page](/libraries/garminconnect). - **garth**. Its README now opens: "Garth is deprecated and no longer maintained." Garmin changed its auth flow, and "New logins will not work", although a saved session may keep working until its token expires. See [garth](/libraries/garth) and [garminconnect vs garth](/libraries/compare/garminconnect-vs-garth). Our recommendation, as judgement rather than Garmin's: for a script or dashboard over your own data, start with the Personal API. It is Garmin's own route, you accept its terms directly, and you never hand your Garmin password to a third-party library. Reach for garminconnect only if the Swagger documentation shows that the Personal API does not expose something you need, and read the Personal API terms first. ## Building for other people instead The Personal API is the wrong tool for a product: Garmin says it is "not intended for commercial applications serving multiple end users". For that, request the Connect Developer Program (the [Garmin API integration guide](/integrate/garmin-api) covers the technical side) or reach Garmin data through an aggregator; the [Garmin API alternatives](/alternatives/garmin-api-alternatives) compares those routes. ## Sources - [developer.garmin.com/gc-developer-program/personal/personal-faq/](https://developer.garmin.com/gc-developer-program/personal/personal-faq/) — personal use, who it is for, not for commercial multi-user apps, key expiry, token lifetime, no refresh tokens, revocation (checked 2026-10-22) - [developer.garmin.com/gc-developer-program/personal/personal-api/](https://developer.garmin.com/gc-developer-program/personal/personal-api/) — key creation steps and the token endpoint (checked 2026-10-22) - [developer.garmin.com/gc-developer-program/enterprise/program-faq/](https://developer.garmin.com/gc-developer-program/enterprise/program-faq/) — personal-use answer, Starter and Enterprise access, OAuth 2.0, approval and Developer Portal (checked 2026-10-22) - [developer.garmin.com/gc-developer-program/overview/](https://developer.garmin.com/gc-developer-program/overview/) — Personal access: own data, data types, pull-only delivery (checked 2026-10-22) - [raw.githubusercontent.com/cyberjunky/python-garminconnect/master/README.md](https://raw.githubusercontent.com/cyberjunky/python-garminconnect/master/README.md) — garminconnect: unofficial client, login, token storage, write methods (checked 2026-10-22) - [raw.githubusercontent.com/matin/garth/main/README.md](https://raw.githubusercontent.com/matin/garth/main/README.md) — garth deprecated, new logins fail (checked 2026-10-22) ## FAQ ### Does Garmin have an API for personal use? Yes, as of October 2026. Garmin's developer site documents the Garmin Connect Personal API, which its FAQ says is available for personal use and lets Garmin customers securely access their own Garmin Connect data. You create the key yourself on Garmin Connect Web; there is no application to approve. Earlier Garmin pages, and earlier pages on this site, described the developer program as business-only. [Permalink](https://aifitnessapi.com/fix/garmin-api-personal-use#faq-1) ### Can I use the Garmin Personal API in an app for other users? No. Garmin's Personal API FAQ says the API is intended for individual Garmin users who want programmatic access to their own data and is not intended for commercial applications serving multiple end users. An app that reads other people's Garmin data belongs in the Garmin Connect Developer Program, which Garmin describes as designed for organizations building integrations for multiple users. [Permalink](https://aifitnessapi.com/fix/garmin-api-personal-use#faq-2) ### How long does a Garmin Personal API access token last? Garmin says access tokens are valid for 24 hours or until the Personal API key expires, whichever comes first, and refresh tokens are not supported, so you request a new token from the same endpoint. The key itself can be set to expire after 30 days, 90 days, 180 days or one year, and Garmin emails a reminder about a week before it expires. [Permalink](https://aifitnessapi.com/fix/garmin-api-personal-use#faq-3) ### What data does the Garmin Personal API include? Garmin's program overview lists activity data in JSON and .FIT, health data in JSON and women's health data in JSON, delivered pull only. The exact endpoints are in Garmin's Personal API Swagger documentation, which builds in the browser and which our October 22, 2026 snapshot could not capture, so check it before you plan around a specific metric. [Permalink](https://aifitnessapi.com/fix/garmin-api-personal-use#faq-4) ### Should I still use garminconnect or garth for my own Garmin data? garth is out: its README says it is deprecated and new logins will not work. garminconnect still works by its own account, but its README calls it an unofficial client that signs in with your Garmin username and password. Our view is to start with Garmin's official Personal API and keep garminconnect for data the Personal API turns out not to expose. [Permalink](https://aifitnessapi.com/fix/garmin-api-personal-use#faq-5)