Health Connect SDK: 32 Releases, One Stable
Google has shipped 32 connect-client releases since August 2022 and one stable build, 1.1.0. The alpha runs, gaps and cadence, counted from the notes.
Wearables, health data, nutrition, AI motion tracking — compared, priced, and documented down to the failure modes, with the deprecations and deadline traps called out before they cost you a rewrite.
A fitness API is a service that lets your application programmatically retrieve fitness or health data, or invoke a fitness capability, without building the underlying data pipeline yourself. Most are HTTP/REST web services you call over the network; a key exception is on-device health stores like Apple HealthKit and Google Health Connect, which you reach through the phone's operating system rather than a remote server. It is a category, not a single product: exercise-content databases, wearable-metric APIs, nutrition APIs, AI-motion SDKs, and aggregators are all fitness APIs, each solving a different job. What a fitness API is goes further.
| API | Category | How it bills you | Approval gate | Cost on the user’s side |
|---|---|---|---|---|
| Fitbit Web API (Google) | Wearable APIs (direct) | Free | Yes | Yes |
| Garmin Health / Activity API | Wearable APIs (direct) | Free | Yes | Yes |
| Oura Cloud API | Wearable APIs (direct) | Free | Yes | Yes |
| WHOOP Developer Platform | Wearable APIs (direct) | Free | Yes | Yes |
| Strava API | Wearable APIs (direct) | Free | Yes | Yes |
| Polar Open AccessLink | Wearable APIs (direct) | Free | None documented | Yes |
| Terra | Health-data aggregators | Usage-based | Yes | None documented |
| Junction (formerly Vital) | Health-data aggregators | Usage-based | None documented | None documented |
| Rook | Health-data aggregators | Usage-based | Yes | None documented |
| Spike | Health-data aggregators | Usage-based | Yes | None documented |
| Apple HealthKit | Platform health stores | Free | Yes | None documented |
| Google Health Connect | Platform health stores | Free | Yes | None documented |
| Nutritionix | Nutrition & food data | Free tier | Yes | None documented |
| Edamam | Nutrition & food data | Free tier | None documented | None documented |
| USDA FoodData Central | Nutrition & food data | Free | None documented | None documented |
| Open Food Facts | Nutrition & food data | Free | None documented | None documented |
| ExerciseDB (AscendAPI) | Exercise content | Free tier | None documented | None documented |
| wger (self-hosted) | Exercise content | Free | None documented | None documented |
| KinesteX | AI motion / coaching SDKs | Contact sales | Yes | None documented |
| Sency (SMKit) | AI motion / coaching SDKs | Usage-based | Yes | None documented |
| QuickPose | AI motion / coaching SDKs | Free tier | None documented | None documented |
| MediaPipe Pose Landmarker (BlazePose) | Pose-estimation models | Free | None documented | None documented |
| TensorFlow MoveNet | Pose-estimation models | Free | None documented | None documented |
| Apple Vision body pose | Pose-estimation models | Free | None documented | None documented |
Each row opens the product’s entry in the fitness API list, with what each gate and cost is and every page here that covers it, or compare any two side by side. “None documented” means none in the sources we checked, not that none exists. KinesteX funds this site and is listed by the same rule as every other product.
Compare the field by the job you’re hiring for — data coverage, pricing model, approval gates — before you write a line of integration code.
Camera rep counting, form feedback, LLM coaching — the whole pipeline from pose model or SDK choice to guardrails, latency, and cost.
401s, dead webhooks, empty reads — symptom-to-fix pages. And when a platform is being retired, the dated migration playbook is already written.
Handed a whole job rather than one question? 4 reading paths put the pages for one task in working order, with a sentence per step on why it comes there.
One page per API: how it bills you, what your users must own, what gates launch.
Browse itThree questions, a tailored recommendation with next steps — and the reasoning shown.
Try itModel what your stack costs at your user count — every price traced to its source.
Plan costsEvery metric’s HealthKit ↔ Health Connect type — and where they quietly disagree.
Open itWatch a naive daily rollup break on DST and timezones — interactively, then fix it.
See it breakPaste an error string; get the matching HKError.Code case in Apple’s wording, plus the guide that covers it.
Diagnose itAnswer four questions; get the HealthKit types and APIs that survive them, with the exclusions shown.
Generate itPlus the aggregation checker, identifier translator, permission builder and query generator — all on one page, all running in your browser.
See every toolGenerated, not written. Every value below is read from Apple’s documentation JSON or verified against both platforms’ docs, and regenerating the dataset updates every page that cites it.
All 241 identifiers across 12 group pages — the unit each comes back in, whether you sum or average it, iOS availability, and the Health Connect record where one is verified.
Open the referenceQuantity, category, characteristic and workout identifiers — with units, availability, and whether you sum or average each one.
Open the referenceWhat each failure means — including why a denied read raises no error at all, and returns an empty result instead.
Open the referenceThe cross-platform mapping for the metrics we verified on both, and the pairs that look equivalent but are not.
Open the referenceAlso in the reference: HealthKit by iOS version · Health Connect record reference · Every Health Connect permission · Open-source health libraries
193 of 432 pages were re-checked against their sources in the last 30 days, and these are the most recently verified entries in the changes tracker. Both numbers are computed at build time from the pages themselves — if we stop doing the work, this section says so.
Every price, limit, and deadline traces to a primary source checked when the page was written. When we can’t verify a claim, the page says so instead of rounding up to certainty. How we verify →
The changes tracker labels every deadline confirmed — vendor’s own words, quoted — or reported, and keeps each date at the precision its evidence supports. See the tracker →
Cookbook recipes are dependency-free files with node:test suites, run in CI on every change — the code on the page is a byte-verbatim copy of the file that passed. Open the cookbook →
KinesteX, an AI motion SDK, funds this site. Every page that features it says so in a banner like this one, our comparisons list where its competitors win, and nothing here ever crowns the sponsor. Read the rules we follow →
The year the free ride ended: shutdowns, paywalls, and model freezes across the ecosystem — what changed, what it costs now, and where the risk sits next.
Read the report →Pricing, access models, and status for the ecosystem in one dataset — CC BY 4.0, so you can cite it, load it, or build on it.
When a reported date firms up or a term changes, subscribers hear first — with the source, not the panic. Join them below ↓
Google has shipped 32 connect-client releases since August 2022 and one stable build, 1.1.0. The alpha runs, gaps and cadence, counted from the notes.
118 of Health Connect's 219 framework permissions are symptom strings added at API level 37. Read vs write, medical, background and history, counted.
5 of 24 products bill your end user, not you. All five are direct wearable integrations, and the hardware requirement, not your budget, sets your reach.
Sign up and the downloads appear instantly: the API selection checklist, the launch compliance checklist, the motion-SDK scorecard, and the full 2026 dataset. After that, one email when something actually changes — a deadline, a term, a deprecation. No fluff, no spam.