Since March 2026 Garmin has refused requests to Garmin Connect that do not come from a browser, through Cloudflare and with the status 403, even when the request carries valid session cookies; we measured this on 13 September 2026. On top of that, Garmin limits sign-ins per account with the status 429, so an app that signs in again and again runs into a second refusal.
What does a 403 mean for you?
That Garmin turned the request away because of how it was sent, not because of your account. In our measurement on 13 September 2026, a request from the iPhone’s standard network interface (URLSession) received 403 with valid session cookies, and also with exactly the headers that Garmin’s own web app sends. The password and the session were valid in that case. For you this means that your sign-in details were right, and that typing them in again changes nothing about how the next request is sent.
What does a 429 mean for you?
That Garmin has seen too many sign-ins for your account. Garmin limits sign-ins per account, so an app has to sign in once, keep the session and never sign in again just in case. A 429 is about the number of sign-ins, not about whether they were correct.
Why does entering the password again not help?
Because neither status is about the password. A 403 rejects the way a request is sent, so the same kind of request after a fresh sign-in meets the same 403; a 429 counts sign-ins, so each new attempt adds one more. RunGap’s App Store version history, read on 12 September 2026, shows the same direction: version 26.1 of 12 January 2026 brought Garmin’s sign-in page into the app and noted that Cloudflare checks can make sign-ins more frequent. RunGap’s App Store listing carries this history. Which other apps write to Garmin Connect is in RunGap alternatives for Garmin Connect.
Why do sync apps not use an official Garmin interface?
Because Garmin offers none for uploading activities from such an app. The Garmin Connect Developer Program is free, but open only to companies, and it has no upload. A sync app that writes to Garmin Connect therefore signs in to your account the way you do on the website, and that is the sign-in Garmin checks.
How does Nabe sign in without seeing your password?
On Garmin’s own sign-in page, which Nabe opens inside the app in a browser view (WKWebView), and every later request to Garmin Connect runs through that same browser view. The 403 does not apply there: on 13 September 2026 Nabe uploaded a test ride this way, and Garmin answered with 202 and listed the ride.
Nabe keeps the session Garmin issues (Remember Me) in the iPhone’s keychain and does not sign in again on suspicion. When the session has expired, Nabe shows a card that opens Garmin’s sign-in page; iOS AutoFill can fill it in from your own keychain, which Nabe cannot read. Nabe stores no Garmin password and reads none. From the browser view Nabe uses the headers of Garmin’s web app, among them the session’s security token (CSRF), but no password and no form fields. Signing out deletes the Garmin sign-in, the device identity and the Garmin list on the iPhone.
Nabe uses this session to upload rides from Wahoo and Hammerhead. The way from a Karoo is in how Hammerhead Karoo rides get to Garmin Connect, the way from a Wahoo in how to sync Wahoo rides to Garmin Connect.