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¶
| Feature | Garmin Connect | Intervals.icu |
|---|---|---|
| Activities | ✅ | ✅ |
| Activity history backfill | ✅ 5 years | ✅ 5 years |
| Dailies | ✅ | — |
| Workout fanout | ✅ running only | — |
Future integrations¶
Wahoo, Polar Flow, Suunto, Apple Health, and Coros are on the roadmap. The unified data model is designed so adding a platform is a SweatStack change: your code does not need to change when a new platform comes online.
Which integration ships next is driven by demand. If one of these is blocking your integration, let us know so we can weight it accordingly. We also build custom integrations on request.
Backfill¶
When a user connects a platform, ingestion starts immediately. SweatStack processes roughly 50-100 hours of activity data per minute, so a typical user's full history lands within a minute or two. Very large accounts with many years of data can take a few minutes longer, depending on the source platform's sync speed.
Progress is shown to the user during the SweatStack Connect onboarding flow. Apps that need to know programmatically when backfill is complete can poll the backfill status endpoint. See GET /api/v1/activities/backfill-status in the API reference, or the activities → backfill status page for the worked Python and cURL examples.
UX recommendation. Let users into your app immediately and show a progress indicator for the first session. Gating the first session on full backfill completion adds friction without payoff: by the time they've finished signing up and clicking around, most of the data they care about is already in.
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.