Skip to content

API reference

Every public HTTP endpoint and response schema for app.sweatstack.no, generated from the canonical OpenAPI spec at https://app.sweatstack.no/openapi.json. Rebuilds with the docs, so it can't drift from the API.

Want to call the endpoints right now?

Use the API playground. It picks up your logged-in SweatStack session, so there's no API token to mint or paste. The reference here is for reading the spec. The playground is for running requests.

An endpoint in beta has "(beta)" at the end of its summary, and its operation in the OpenAPI spec carries x-beta: true, so your tools can tell it apart from a stable one. Its description starts with the beta notice. A beta endpoint is subject to breaking changes. If you plan to use one in production, email info@sweatstack.no before you integrate.

Reference by resource

  • Activities: list and read a user's activities, including timeseries data and longitudinal queries across many activities at once. Accumulated work duration is in beta.
  • Traces: point-in-time measurements like lactate or RPE, attached to activities by timestamp.
  • Tests: structured performance evaluations with a defined results schema (lactate, VO2max, FTP).
  • Dailies: once-per-day measurements such as body mass, resting heart rate, HRV, and sleep.
  • Profile: metabolic profile, account status, sports hierarchy, and tags for the current user. The metabolic profile and the account status are in beta.
  • Users: user-account operations.
  • App users: the users that belong to your app, created and managed by the app with its client credentials (beta). See Choosing how athletes connect.
  • Teams: team management for organizations and groups.
  • Pages: the SweatStack Pages hosting product.
  • Portal: links to the SweatStack Portal for your users (beta).
  • OAuth: authorization, token issuance, and OpenID discovery. The issue claim on userinfo is in beta.
  • Workouts: workout scheduling and library (beta).
  • Data: concept-level explanations, when to use what, with curated examples.
  • Guides: end-to-end patterns like incremental sync, native mobile apps, and the onboarding flow.
  • API playground: interactive Try-It with your account.