One normalised schema
Activities, daily summaries, body metrics and nutrition arrive in one consistent, SI-unit shape — no matter which provider they came from.
CaterFit is a normalised wearable-data API for fitness and non-clinical wellness software. One consistent feed of the wearable & nutrition data your users already track — at a price that makes sense before you’re an enterprise. Coaching teams are our first focus.
No credit card. We’re onboarding a small number of design partners first.
We keep the surface area small on purpose: the essentials a coaching product actually needs, done well — one schema, the major ecosystems, and multi-tenant safety baked in.
Activities, daily summaries, body metrics and nutrition arrive in one consistent, SI-unit shape — no matter which provider they came from.
Start with the sources your athletes already use. We add partner-gated providers as vendor approvals land, so your roadmap isn't blocked on one integration at a time.
Row-level security, per-customer API keys, encrypted token storage and an audit trail are built in from day one, not bolted on later.
Vendor pushes are de-duplicated and idempotent. One provider's outage never blocks another's sync — isolation is a core invariant.
Predictable REST, stable error codes you can write retry logic against, and no surprise vendor-specific fields leaking into your data.
Pay for connected users, not per API call. A low, transparent floor plus a small per-user rate that scales with you — see pricing below.
We won’t claim “500+ devices” on day one. Here’s exactly where each integration stands today — lead providers first, then the partner-gated and on-device sources as approvals land. If a provider’s terms don’t allow us to offer it, we say so plainly (see the FAQ on Strava).
Provider availability depends on each vendor’s current terms and approvals, which can change. Partner-gated and on-device providers may require your own registration, an active membership, or written provider approval before use. Strava is not offered through CaterFit — see the FAQ.
A couple of providers can’t be resold through an API like ours under their current terms. Here’s what that means for you and how your users still connect them.
No. Strava is not a supported provideron CaterFit — we don’t connect, store, normalise or resell Strava data to your product, and we don’t list it as an available integration.
Strava’s API terms don’t allow a third-party “aggregator” like CaterFit to fetch Strava data and pass it through to another app. They also only permit an athlete’s Strava data to be shown to that same athlete — not to a coach or anyone else, even withthe athlete’s consent. We’d rather tell you that plainly than ship something that gets your app cut off.
They connect Strava directly to a Strava-compliant integration you run yourself, under your ownStrava API agreement — not through CaterFit. Note that even then, Strava’s standard terms let you show an athlete their own Strava data in an athlete-facing experience; they do notlet you surface that data to a coach or any third party without a separate written agreement from Strava. Registering your own app doesn’t change that — so plan for an athlete-facing view, not a coach dashboard, for Strava data.
If your athletes also wear a Polar, Withings or other supported device, CaterFit gives you a normalised feed of thatdata — so you still get one consistent shape for everything we’re allowed to carry.
Not yet. Oura is approval-gated: using its API through an aggregator needs a written agreement and, in Oura’s model, per-end-customer approval. CaterFit can’t obtain or imply those approvals on your behalf, and connecting an ordinary consumer Oura account isn’t enough on its own.
We’re pursuing the correct partner path with Oura. Until a written agreement is in place we keep Oura marked partner approval requiredrather than pretending it’s live.
For some providers we can, and we’re working through the proper partner agreements (that’s what “partner approval required” means on the provider list). But an agreement has to actually permit the thing we’d be doing — aggregating, storing a normalised history, and exposing it to your product.
For Strava specifically, the standard terms prohibit that aggregator model outright, so there’s no honest way to offer it today. If that ever changes with a negotiated written agreement, we’ll update this page — we won’t advertise it before then.
A low flat floor, then a small per-user rate as you grow. We meter on connected users — never per API call, so good engineering isn’t taxed and there’s no cliff that punishes you the moment your app takes off.
Concierge pilot for the first few design partners.
Grows with you — built for apps with real volume.
Custom contracts, bespoke provider work, security review.
Indicative estimate (AUD) on the Scale tier — predictable, linear pricing with no user cliff. No live checkout yet.
Prices are indicative (AUD) and shown to signal intent — there is no live checkout yet. Final pricing is set after our first design partners.
We’re onboarding a small group of coaching & fitness software teams as design partners. Tell us what you’re building and we’ll be in touch.