Integrations

SweatStack ingests activity, daily, and test data from wearable platforms and routes it through a single normalized API. Your app authenticates against SweatStack once. The platform handles the rest.

Supported today

Platform	What you get
Garmin Connect	Activities (full timeseries), dailies, historical backfill.
Intervals.icu	Activities (full timeseries), dailies, tests. Useful as a proxy for any platform Intervals.icu supports (except Strava; see below).

Coming soon

Polar Flow, Apple Health, Wahoo, Coros, Suunto. The unified data model is designed so adding a platform is a backend change. Your code does not change when a new platform comes online.

Why not Strava

Strava's terms prohibit forwarding activity data through a third-party API. SweatStack cannot integrate directly, and platforms that proxy Strava (e.g. Intervals.icu) cannot legally forward Strava-origin activities to SweatStack either. The recommended workaround for end users is to connect their wearable directly. Background: Strava privacy update.

How users connect

End users link platforms in their SweatStack account at app.sweatstack.no/settings/sharing. For your onboarding flow, you typically don't need to think about this. SweatStack Connect lets users authenticate via the wearable account they already have, and SweatStack handles the platform link.

What this means for your code

One activity API across every supported platform. Same shape regardless of source. See data model for the schema and activities for query patterns.