Garmin
Garmin signs in per athlete. Each athlete approves access to their own data, and KoraBridge stores their tokens encrypted.
Connect Garmin
- Open the Athletes page and invite the athlete, choosing Garmin as the connector.
- Send the consent link to the athlete. They approve access on Garmin.
- The consent status changes from pending to approved. Add the connection and use it in a pipeline.
You can revoke an athlete's consent at any time from the Athletes page.
What it syncs
| Stream | Contents |
|---|---|
| Activities | Activity sessions such as runs and rides |
| Daily summaries | Daily wellness and activity summaries |
| Sleep data | Sleep sessions and staging |
| Heart rate | Heart rate time series |
All streams are on by default.
Fields
Access token
The OAuth2 bearer token from the consent flow. The consent flow fills it in for you. Paste one by hand only for testing.
Start date
Data is pulled from this date onwards. The default is 1 January 2020.
End date
Only data at or before this date is synced. Leave it blank to sync up to now.
Webhooks
Garmin can also push data to KoraBridge. Each Garmin connection has its own webhook URL with a secret token in the path, and deliveries that fail signature validation are rejected. Duplicate detection on webhook deliveries is best effort, so key your downstream tables on Garmin's own identifiers.