Skip to content

Garmin Authentication - Service Ticket

Only use this if the normal sign-in is not working

Garmin periodically changes how their login page works, which can prevent P2G from signing in automatically. This page walks you through an alternative method that works even when the standard sign-in fails.

If your automatic syncs are working fine, you do not need to do anything here.

Page generated with AI assistance

This page was generated with the help of Claude AI. The happy path via the Settings UI has been explicitly tested. Other flows (config file, environment variable) have not been fully verified — please open an issue if you run into problems.

What is this?

Normally P2G signs into Garmin automatically using your email and password. When Garmin blocks this (for example with a Cloudflare challenge), P2G can no longer authenticate on its own.

This guide walks you through a manual one-time process:

  1. You log into Garmin in your browser and copy a short-lived code called a service ticket
  2. You give that code to P2G (via the Settings UI, a config file, or an environment variable)
  3. P2G immediately exchanges it for a long-lived token and stores it securely

Once this is done, P2G handles daily syncs automatically for approximately 30 days, after which you will need to repeat this process.

Step 1: Get a Service Ticket from Garmin

You will retrieve the service ticket directly from your browser. This takes about 2 minutes.

The service ticket will expire, possibly within 1 minute — move quickly once you have it.

  1. Open a new browser tab
  2. Press F12 (Windows/Linux) or Cmd+Option+I (Mac) to open Developer Tools
  3. Click the Network tab at the top of the Developer Tools panel
  4. In the filter/search box, type mobile/api/login to narrow down the results
  5. Navigate to this exact URL and log in with your Garmin credentials: 
    https://sso.garmin.com/mobile/sso/en_US/sign-in?clientId=GCM_ANDROID_DARK&service=https://mobile.integration.garmin.com/gcm/android
    !!! note "The page may not look like it loaded correctly — that is normal. As long as you were able to enter your credentials and submit the form, the ticket will appear in the Network tab."
  6. After logging in, look in the Network tab for a request that includes mobile/api/login
  7. Click that request, then open the Response or Preview tab

  8. Find the value next to "serviceTicketId" — it looks like ST-XXXX-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-sso

    If the Response tab appears empty, right-click anywhere in the Network tab and choose Save All As HAR. Open the downloaded file in a text editor (e.g. Notepad) and search for serviceTicketId to find your ticket.

  9. Copy the full value (do not include the surrounding quotes)

Step 2: Give the Service Ticket to P2G

Jump to the instructions for your install method:

Install Method Instructions
Windows App Via the Settings UI
Docker (Web UI) Via the Settings UI
Web UI (from source) Via the Settings UI
Docker (Headless) Via config file
GitHub Actions Via config file
Console Via config file

Via the Settings UI

For: Windows App, Docker (Web UI), Web UI (from source)

  1. Open P2G and go to Settings → Garmin
  2. Open the Advanced section
  3. Paste your service ticket into the Service Ticket field
  4. Click Save

P2G will immediately exchange the ticket for a long-lived token. If it succeeds, the "Service Ticket is set" badge will disappear (the ticket has been consumed) and your next sync will work automatically.

Via config file

For: Docker (Headless), GitHub Actions, Console

Add the ServiceTicket field to the Garmin section of your configuration.local.json:

"Garmin": {
  "Email": "your@email.com",
  "Password": "yourpassword",
  "ServiceTicket": "ST-XXXX-paste-your-ticket-here",
  "Upload": true
}

Start or restart P2G immediately after saving so the ticket is consumed before it expires. P2G will exchange it on startup and automatically remove it from your settings — you do not need to remove it manually.

After 30 days

The long-lived token P2G stores lasts approximately 30 days. After that, syncs will fail with an authentication error. When that happens, simply repeat this process from the beginning.

P2G will log a message like NeedServiceTicket to let you know it is time to re-authenticate.