Learn¶
Concepts and reference material for building on SweatStack. If you haven't yet, do the quickstart first. Fifteen minutes, working app.
Start here¶
- Data model: the shape of every entity in SweatStack and how they relate. Read this first; everything else assumes it.
- Authentication: OAuth2 and OpenID Connect, scopes, JWTs, JWKS. The standard flow your app uses.
Data¶
- Activities: per-activity timeseries and longitudinal queries across a user's history.
- Dailies: body mass, resting heart rate, HRV, sleep. Date-keyed measurements.
- Tests: structured performance evaluations (lactate, VO2max, FTP) with a defined results schema.
- Metabolic profile: thresholds, training zones, intensity-duration models. Built from tests plus training data.
- App metadata: attach per-app JSON to activities, traces, tests, and users. Skip running your own database.
Onboarding¶
- SweatStack Connect: productized "Continue with SweatStack" onboarding. Users authenticate via the wearable they already use.
- Managing apps: register an OAuth2 application, configure redirect URIs, manage credentials.
Platforms¶
- Integrations: supported wearable platforms (Garmin, Intervals.icu) and the roadmap.
- SweatStack Pages: host your app's frontend on
*.pages.sweatstack.devwithout standing up infrastructure.
Events¶
- Webhooks: subscribe to real-time events when activities or tests are created, updated, or deleted. HMAC-SHA256 signed.
Build with¶
- AI coding: skills for AI agents, OpenAPI schema, prompting tips. The fastest way to ship working SweatStack code.
- Python SDK: the official client. Class-based and module-level interfaces.
- CLI: manage apps and deploy to Pages from the terminal.
- Frameworks: drop-in helpers for FastAPI, Streamlit, and Jupyter.
- Tools: in-browser Console REPL, sharable Python playground.