Integrations & data sources

Hevy Pro required

Hevy only provides API keys to users with an active Pro subscription. If you cannot find your API key in Hevy's settings, this is likely why. The API key is found under Profile > Settings > API.

API stability

Hevy is a smaller platform and their API is not covered by a formal developer agreement or SLA. They have been transparent that they make no guarantees about the API's structure or long-term availability. We monitor for changes and will update the integration if anything breaks.

7-day storage rule

Strava's terms prohibit storing activity data for more than 7 days. FitMesh cannot build a long-term history from Strava data alone — we re-fetch your recent activities each time rather than keeping a permanent archive.

Can't combine with other sources

Strava's 2024 API agreement explicitly prohibits combining their data with data from other platforms. This limits how we can show Strava activities alongside your Hevy, Garmin, or Google Fit data in a unified timeline.

Athlete quota — pending approval

Strava's sandbox mode limits an app to one connected athlete at a time until the API application is formally reviewed and approved. FitMesh is currently in that sandbox — meaning only one Strava account can be connected at a time while we await approval. The integration itself works; it's just restricted in scale until Strava signs off.

Google Fit is being deprecated

Google stopped accepting new developer signups for the Fit API in May 2024 and has announced a full shutdown, likely in 2026. Existing connections will continue to work until then.

Health Connect is the replacement — but there's a problem

Google's technical replacement for the Fit REST API is Health Connect, which is a local Android API with no cloud equivalent. Web apps like FitMesh cannot access it. The Fitbit Web API is a separate cloud API that we plan to connect to, but it does not replace Google Fit for existing users.

What this means for you

Your Google Fit connection will keep working for now. We will give plenty of notice before anything changes, and we are working on a data export so your history is preserved.

Proper open API — no barriers

Polar provides an open developer programme with full OAuth 2.0. Any developer can register an app and start pulling data immediately — no business partnership or waiting for approval required.

What syncs

Training sessions, GPS routes, heart rate, V̇O₂ max estimates, sleep, nightly recharge, and daily activity. Polar watches have excellent physiological metrics and all of it flows through.

Supported devices

All Polar watches that sync to the Polar Flow app — including the Vantage, Pacer, Ignite, Grit, and Unite series.

No self-serve access

Unlike Strava or Google Fit, Garmin does not offer a self-serve developer API. Access requires a formal application, business review, and approval from Garmin's developer programme team.

Why we removed the old connection

FitMesh previously used an unofficial, credential-based method to access Garmin data. Garmin's developer agreement explicitly prohibits asking users for their Garmin credentials. We removed this to stay compliant.

What to expect once approved

OAuth-based access to workouts, heart rate, sleep, HRV, training load, recovery, body battery, and more. It will cover everything Garmin Connect tracks.

Why it needs a native app

Apple does not provide a cloud REST API for Health data. The only authorised path is a native iOS app using the HealthKit framework. Web apps cannot reach Health data directly — there is no workaround.

What will sync once available

Workouts from Apple Watch or iPhone (runs, rides, strength, swims), heart rate and HRV, step count, sleep analysis, resting energy, and active calories. Everything the Health app already tracks.

In the meantime

Apple Watch workouts exported to Strava flow through the Strava integration (subject to Strava's sandbox limit — see above). Polar is now live. Once Garmin is live, the majority of watch-based workouts will be covered.

What syncs

Workouts, daily steps, sleep stages, and weight log entries. Connect from the Integrations tab — Fitbit uses OAuth so you will be redirected to sign in and approve access.

Fitbit is Google's fitness brand now

Fitbit now requires a Google account to sign in and powers the Pixel Watch. The Fitbit Web API at api.fitbit.com is separate from the Google Fit REST API and currently operational.

Long-term API stability

Google has not announced a shutdown date for the Fitbit Web API, but the consolidation direction — mandatory Google accounts, Health Connect replacing everything — is worth watching. We will monitor for changes and update the integration if anything shifts.

What Whoop tracks

Recovery score, HRV, resting heart rate, strain, sleep performance, respiratory rate, and blood oxygen. If you use Whoop, this is the data you would want flowing into FitMesh.

API access

Whoop provides an OAuth 2.0 developer API. It requires application approval but is available to third-party developers. Straightforward to integrate once we get to it.

What Oura tracks

Sleep stages, readiness score, HRV, body temperature, activity, and resting heart rate. The Oura API is RESTful and uses personal access tokens — straightforward to integrate.

What it covers

Cycling workouts, power data, heart rate, and workout files from Wahoo devices. The API uses standard OAuth 2.0 and is open to third-party developers.