garmin-auth
Self-healing Garmin Connect authentication for Python, with 2FA/MFA support.
Wraps garminconnect>=0.3.0 with token persistence, retry-aware rate limiting, and a CLI so you don't have to re-plumb auth for every project.
Why?
The upstream garminconnect library handles the login flow but leaves token persistence, 2FA resume, and rate limit recovery to the caller. This package wraps it with:
- 2FA/MFA support — pass a
prompt_mfacallback for blocking CLIs, or usereturn_on_mfa=True+resume_login(code)for async/web flows - Token persistence — survives ephemeral CI runners via file (
~/.garminconnect/garmin_tokens.json) or PostgreSQL storage - Rate limit handling — retry with backoff on 429
- Zero-config CLI — interactive prompts, saved email, friendly output
Install
pip install garmin-auth
Quick Start
CLI
# First time — prompts for email and password interactively
garmin-auth login
# Check token status
garmin-auth status
# Refresh tokens (for cron jobs / CI)
garmin-auth refresh
# Pass credentials via flags
garmin-auth login --email you@example.com --password yourpassword
# Or via environment variables
export GARMIN_EMAIL=you@example.com
export GARMIN_PASSWORD=yourpassword
garmin-auth login
After first login, your email is saved to ~/.garmin-auth/config.json so you only need to enter your password on subsequent logins.
Python API (no MFA)
from garmin_auth import GarminAuth
# Reads GARMIN_EMAIL/GARMIN_PASSWORD from env, or uses saved tokens
auth = GarminAuth()
client = auth.login() # Returns an authenticated garminconnect.Garmin client
activities = client.get_activities(0, 10)
Python API (MFA, blocking CLI)
# prompt_mfa is called by garminconnect when a second factor is needed.
auth = GarminAuth(
email="user@example.com",
password="...",
prompt_mfa=lambda: input("Garmin MFA code: "),
)
client = auth.login() # blocks on the prompt when MFA is required
Python API (MFA, async/web flow)
auth = GarminAuth(
email="user@example.com",
password="...",
return_on_mfa=True,
)
result = auth.login()
if result == "needs_mfa":
code = wait_for_user_to_enter_code() # your web handler
client = auth.resume_login(code)
else:
client = result
Token maintenance
auth = GarminAuth()
info = auth.status() # {"status": "stored", "has_di_token": True, ...}
auth.refresh() # force a DI token refresh via cached credentials
How It Works
- Cached tokens — on each
login(), the savedgarmin_tokens.jsonis handed togarminconnect.Garmin.login(tokenstore=...), which proactively refreshes the DI OAuth token when it's near expiry. - Fresh credentials — if no tokens exist (or they're rejected), garmin-auth
hands off to
garminconnect, which runs its own 4-strategy fallback (portal+curl_cffi → portal+requests → mobile+curl_cffi → mobile+requests). - MFA — when Garmin returns
MFA_REQUIRED, you either handle it inline viaprompt_mfaor catch"needs_mfa"and callresume_login(code).
Tokens stay fresh automatically; even a fully expired session recovers without manual intervention (assuming the credentials are still valid).
Token Storage
Tokens are saved as garmin_tokens.json inside ~/.garminconnect/ by default
(single-file DI OAuth payload — not compatible with the old oauth1/oauth2 split
used by garmin-auth 0.2.x or by garth).
# Custom token directory
garmin-auth --token-dir /path/to/tokens login
# Custom directory in Python
auth = GarminAuth(token_dir="/path/to/tokens")
For PostgreSQL storage (CI/CD or multi-machine setups):
from garmin_auth import GarminAuth
from garmin_auth.storage import DBTokenStore
auth = GarminAuth(store=DBTokenStore("postgresql://user:pass@host/db"))
Docker
# Build
docker build -t garmin-auth .
# Login (interactive)
docker run -it -v garmin-tokens:/root/.garminconnect garmin-auth login
# Check status
docker run -v garmin-tokens:/root/.garminconnect garmin-auth status
# Refresh (for cron)
docker run -e GARMIN_EMAIL=... -e GARMIN_PASSWORD=... \
-v garmin-tokens:/root/.garminconnect garmin-auth refresh
Development
git clone https://github.com/drkostas/garmin-auth.git
cd garmin-auth
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
pytest tests/ -v
Limitations
- Garmin rate limits — Garmin aggressively rate-limits auth attempts (429). The package handles retries with backoff, but excessive calls in a short period may require waiting 1-24 hours
- First-run upgrade from 0.2.x — the token format changed; users upgrading from garmin-auth 0.2.x must log in again once (cached tokens from the old format are rejected cleanly)
License
MIT
Metadata
Release files for garmin-auth 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| garmin_auth-0.4.0.tar.gz | 46.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| garmin_auth-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.2 kB
Release files / garmin_auth-0.4.0.tar.gz
| Download URL | garmin_auth-0.4.0.tar.gz |
|---|---|
| Size | 46.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b85c9cd5e33846e591c9028aa0ed68d97ab67452f4d7a82e767f96c9e5626974
|
|
BLAKE2b-256 checksum How to use checksums |
8f1d55527ab360d68811540797a669d0a2d386b62b2e58f674d9186625af829a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency logRelease files / garmin_auth-0.4.0-py3-none-any.whl
| Download URL | garmin_auth-0.4.0-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
61b8638f519e1832ec3425bbface6dc0e22652f2ee3e854198d03b21a7a941c9
|
|
BLAKE2b-256 checksum How to use checksums |
ed450ca9869017b7ee2c2a38fe1018ddb9543ada2f946aa498730f2aa8f10521
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 10, 2026.
Transparency log