429 Too Many Requests - during login (OAuth Preauthorized)

[joaoncfsantos]

Hi all,

I have been facing this error with Garmin Connect authentication and I have no idea how to fix it. Am I the only one who's facing this right now?

It seems to be failing specifically on the OAuth preauthorized endpoint.

Traceback:

Logging in to Garmin Connect...
  File "/app/.venv/lib/python3.13/site-packages/garminconnect/__init__.py", line 498, in login
Login failed: 429 Client Error: Too Many Requests for url: https://connectapi.garmin.com/oauth-service/oauth/preauthorized?ticket=ST-2270077-9MyIgeAH1WjPg9JzkUUI-cas&login-url=https://sso.garmin.com/sso/embed&accepts-mfa-tokens=true (status=429)
    return _complete_login(client)
    token1, token2 = self.garth.login(
Traceback (most recent call last):
                     ~~~~~~~~~~~~~~~~^
        self.password,
  File "/app/.venv/lib/python3.13/site-packages/garth/sso.py", line 267, in _complete_login
        self.username,
                                           ~~~~~~~~~^
        ^^^^^^^^^^^^^^
    )
        *args, **kwargs, client=self
        ^^^^^^^^^^^^^^
    ^
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ^
        prompt_mfa=self.prompt_mfa,
    self.oauth1_token, self.oauth2_token = sso.login(
  File "/app/.venv/lib/python3.13/site-packages/garth/http.py", line 203, in login
  File "/app/.venv/lib/python3.13/site-packages/garth/sso.py", line 142, in login
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 429 Client Error: Too Many Requests for url: https://connectapi.garmin.com/oauth-service/oauth/preauthorized?ticket=ST-2270077-9MyIgeAH1WjPg9JzkUUI-cas&login-url=https://sso.garmin.com/sso/embed&accepts-mfa-tokens=true
INFO:     100.64.0.9:15782 - "POST /api/v1/sync/garmin HTTP/1.1" 429 Too Many Requests
    oauth1 = get_oauth1_token(ticket, client)
  File "/app/.venv/lib/python3.13/site-packages/garth/sso.py", line 158, in get_oauth1_token
    resp.raise_for_status()
    ~~~~~~~~~~~~~~~~~~~~~^^
  File "/app/.venv/lib/python3.13/site-packages/requests/models.py", line 1026, in raise_for_status

Environment:
garminconnect version: 0.2.40
Python: 3.13

Has Garmin changed their rate limits or is there a known workaround for this?

[ForrestHong]

I got the same issue recently.

ERROR:garminconnect:Login failed: 429 Client Error: Too Many Requests for url: https://connectapi.garmin.com/oauth-service/oauth/preauthorized?ticket=xxxxxxxxs&login-url=https://sso.garmin.com/sso/embed&accepts-mfa-tokens=true (status=429) 0|garminsync | Traceback (most recent call last): 0|garminsync | File "xxxxxx/test_garmin_account.py", line 27, in init_api_fixed 0|garminsync | garmin.login(tokenstore)

[ForrestHong]

this issue persists when I using the latest offical demo.py,

`$ ./demo.py
📁 Exported data will be saved to the directory: 'your_data'
📄 All API responses are written to: 'response.json'
Attempting to login using stored tokens from: ~/.garminconnect
No valid tokens found. Requesting fresh login credentials.
Email address: test@mail.com
Password:et
Logging in with credentials...

❌ Too many login attempts. Please wait a few minutes before trying again.`

---

I’ve narrowed it down: using the same code and host PC, the issue only occurs when connecting to the Global server (connectapi.garmin.com). When I switch to the China server (--cn / connectapi.garmin.cn), it works perfectly. It seems to be a server-specific compatibility issue with the latest garth version rather than a local environment problem.

[stevedep]

I have the same issue when using a Docker in Azure, but not when I run locally. From where are you running the code?

[ForrestHong]

I have the same issue when using a Docker in Azure, but not when I run locally. From where are you running the code?

I’m experiencing this on both a remote Ubuntu server (Digital Ocean) and a local Windows 11 machine. Interestingly, the error only occurs when connecting to the Garmin Global (internal) servers; everything works fine when connecting to Garmin China.

[cyberjunky]

Its linked to #332

[cyberjunky]

@matin, others, I left the whole oauth and consumer token path alone... I couldn't get it to work anymore from my IP address...

I went full for their new React app (which has a different endpoint "/gc-api") including JWT token. The profile url and some other things changed too.

The oauth1 and oauth2 files are not used anymore, instead a garmin_tokens.json file is used to store all session related stuff. (JWT, csrf_token amoung others)
But the .dumps and .loads methods still handle this.

All my known Garmin methods work and are compatible for the end user.

If people want to try it:

git clone https://github.com/cyberjunky/python-garminconnect
git checkout react

python3 -m venv .venv
source .venv/bin/activate  # On Windows use: .venv\Scripts\activate

pip install requests readchar
pip install -e .

./demo.py

At the second start it should load the tokens from disk, it also should auto refresh the tokens but didn't test that part yet.
Let me know if this work for you.

PS: I cannot guarantee this is the way forward yet, going for a beer now...

[thehijacker]

@matin, others, I left the whole oauth and consumer token path alone... I couldn't get it to work anymore from my IP address...

I went full for their new React app (which has a different endpoint "/gc-api") including JWT token. The profile url and some other things changed too.

The oauth1 and oauth2 files are not used anymore, instead a garmin_tokens.json file is used to store all session related stuff. (JWT, csrf_token amoung others) But the .dumps and .loads methods still handle this.

All my known Garmin methods work and are compatible for the end user.

If people want to try it:

git clone https://github.com/cyberjunky/python-garminconnect
cd python-garminconnect
git checkout react

python3 -m venv .venv
source .venv/bin/activate  # On Windows use: .venv\Scripts\activate

pip install requests readchar
pip install -e .

./demo.py

At the second start it should load the tokens from disk, it also should auto refresh the tokens but didn't test that part yet. Let me know if this work for you.

PS: I cannot guarantee this is the way forward yet, going for a beer now...

It works! I tested your react branch by demo.py only and I was able to login. But just after login I got No data returned from api.get_full_name() (my first test). But I exited demo.py and opened it again so it used saved token and then it worked fine:

Logging in with credentials...
Login successful! Tokens saved to: ~/.garminconnect
Unable to fetch stats for display: Display name is not set. This usually means your Garmin profile is incomplete (new account with no display name configured). Please set a display name at https://connect.garmin.com and try again.

==================================================
🚴 Full-blown Garmin Connect API Demo - Main Menu
==================================================
Select a category:

  [1] 👤 User & Profile
...
  [q] Exit program

Make your selection: Unable to fetch stats for display: Display name is not set. This usually means your Garmin profile is incomplete (new account with no display name configured). Please set a display name at https://connect.garmin.com and try again.

📋 #1 👤 User & Profile - Options
----------------------------------------
  [1] Get full name
...
Make your selection:
🔄 Executing: get_full_name

📡 API Call: api.get_full_name()
--------------------------------------------------
No data returned

I went ahead and implemented this new branch code to my project and fetching data from 4 days back until now was a success! I can again see how poorly I sleep:

Beer is on me tonight. Enjoy.

Edit. Tried to add my sons account but it seems to be too moch for one day:

2026-03-21 22:59:33,242 garminconnect ERROR Login failed
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/dist-packages/garminconnect/__init__.py", line 454, in login
    mfa_status, _legacy_token = self.client.login(
                                ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/dist-packages/garminconnect/client.py", line 144, in login
    raise GarminConnectTooManyRequestsError("429 Rate Limit")
garminconnect.exceptions.GarminConnectTooManyRequestsError: 429 Rate Limit

Will try again in morning.

[cyberjunky]

@matin, others, I left the whole oauth and consumer token path alone... I couldn't get it to work anymore from my IP address...
I went full for their new React app (which has a different endpoint "/gc-api") including JWT token. The profile url and some other things changed too.
The oauth1 and oauth2 files are not used anymore, instead a garmin_tokens.json file is used to store all session related stuff. (JWT, csrf_token amoung others) But the .dumps and .loads methods still handle this.
All my known Garmin methods work and are compatible for the end user.
If people want to try it:

git clone https://github.com/cyberjunky/python-garminconnect
cd python-garminconnect
git checkout react

python3 -m venv .venv
source .venv/bin/activate  # On Windows use: .venv\Scripts\activate

pip install requests readchar
pip install -e .

./demo.py

At the second start it should load the tokens from disk, it also should auto refresh the tokens but didn't test that part yet. Let me know if this work for you.
PS: I cannot guarantee this is the way forward yet, going for a beer now...

It works! I tested your react branch by demo.py only and I was able to login. But just after login I got No data returned from api.get_full_name() (my first test). But I exited demo.py and opened it again so it used saved token and then it worked fine:

Logging in with credentials...
Login successful! Tokens saved to: ~/.garminconnect
Unable to fetch stats for display: Display name is not set. This usually means your Garmin profile is incomplete (new account with no display name configured). Please set a display name at https://connect.garmin.com and try again.

==================================================
🚴 Full-blown Garmin Connect API Demo - Main Menu
==================================================
Select a category:

  [1] 👤 User & Profile
...
  [q] Exit program

Make your selection: Unable to fetch stats for display: Display name is not set. This usually means your Garmin profile is incomplete (new account with no display name configured). Please set a display name at https://connect.garmin.com and try again.

📋 #1 👤 User & Profile - Options
----------------------------------------
  [1] Get full name
...
Make your selection:
🔄 Executing: get_full_name

📡 API Call: api.get_full_name()
--------------------------------------------------
No data returned

I went ahead and implemented this new branch code to my project and fetching data from 4 days back until now was a success! I can again see how poorly I sleep:

Beer is on me tonight. Enjoy.

Edit. Tried to add my sons account but it seems to be too moch for one day:

2026-03-21 22:59:33,242 garminconnect ERROR Login failed
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/dist-packages/garminconnect/__init__.py", line 454, in login
    mfa_status, _legacy_token = self.client.login(
                                ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/dist-packages/garminconnect/client.py", line 144, in login
    raise GarminConnectTooManyRequestsError("429 Rate Limit")
garminconnect.exceptions.GarminConnectTooManyRequestsError: 429 Rate Limit

Will try again in morning.

Thanks for the beer, appreciated!

I added a small retry, maybe you are too fast getting the name after login and the tokens are not known at all server endpoints.

[jelmerk]

do you have any idea when this will make it in a release. all of my pipelines have been broken since march 18

[cyberjunky]

do you have any idea when this will make it in a release. all of my pipelines have been broken since march 18

I'm still tweaking it, this morning i has an issue again, changed user agent code, I'm still not sure if this is going to work for non interactive scripts/my home assistant integration etc
I also still look into getting the former oauth flow working again.

[thehijacker]

Just a status report. Since switching to react branch (initial commit) it is working great for all my three Garmin accounts. I sync data every hour for last two days. Zero errors. Should I use latest commit from react branch or leave it as it is since it is working? What way do you think your wil go? React or back to using Garth once it is fixed? Thank you @cyberjunky for all the hard work you put into this project.

[cyberjunky]

Just a status report. Since switching to react branch (initial commit) it is working great for all my three Garmin accounts. I sync data every hour for last two days. Zero errors. Should I use latest commit from react branch or leave it as it is since it is working? What way do you think your wil go? React or back to using Garth once it is fixed? Thank you @cyberjunky for all the hard work you put into this project.

Of the current react code is working there is not need to update, it works for short queries, but not for scripts running 24/7 since the tockens/cookies are not long lived. The more I learn what has changed the less confident I am we can go back to old situation unfortunatly.