Skip to content
AF

Awesome Fitness APIs: the list, generated from sourced data

A list of 24 fitness and health APIs and platforms, 20 open-source libraries, 176 MCP servers, 19 open datasets and 44 free tools for developers building with wearable, health and workout data. Generated from aifitnessapi.com's sourced data by a script, so every line restates a published fact and nothing is ranked.

AWESOME.md on GitHubMarkdown copyThe datasets behind it

APIs and platforms

Every product in the site's API directory, by category, with how it bills developers (Free, Free tier, Usage-based or Contact sales) and whether its entry names a review, approval or declaration before production. Each link is the product's directory page, which cites the pages that verify it.

Wearable APIs (direct)

Health-data aggregators

  • Terra — Developer billing: Usage-based. An approval, review or declaration stands before production.
  • Junction (formerly Vital) — Developer billing: Usage-based.
  • Rook — Developer billing: Usage-based. An approval, review or declaration stands before production.
  • Spike — Developer billing: Usage-based. An approval, review or declaration stands before production.

Platform health stores

  • Apple HealthKit — Developer billing: Free. An approval, review or declaration stands before production.
  • Google Health Connect — Developer billing: Free. An approval, review or declaration stands before production.

Nutrition & food data

Exercise content

AI motion / coaching SDKs

  • KinesteX — Developer billing: Contact sales. An approval, review or declaration stands before production. KinesteX funds aifitnessapi.com; it is listed the same way as every other product.
  • Sency (SMKit) — Developer billing: Usage-based. An approval, review or declaration stands before production.
  • QuickPose — Developer billing: Free tier.

Pose-estimation models

Libraries and SDK bridges

Open-source packages for HealthKit, Health Connect and vendor web APIs, read from their registries on 2026-10-03. Each links its registry page; the license is the one the registry states.

React Native

  • react-native-health — The long-standing React Native bridge to Apple HealthKit, and the one this site's SDK release tracker follows. npm, license MIT.
  • @kingstinct/react-native-healthkit — The other React Native HealthKit binding, typed close to Apple's own identifiers — the usual alternative to react-native-health. npm, license MIT.
  • react-native-health-connect — The React Native wrapper for Android Health Connect; since v4 it also carries the Expo config plugin. npm, license MIT.
  • expo-health-connect — Still in many Expo app.json files. Deprecated in the registry and merged into react-native-health-connect v4 — the page exists to say how to remove it. npm, license MIT. Deprecated on npm: Merged into react-native-health-connect v4 — remove this package, replace the expo-health-connect entry in your app.json plugins array with react-native-health-connect, then re-run expo prebuild --clean. See https://github.com/matinzd/react-native-health-connect. Repository archived on GitHub.
  • react-native-google-fit — The React Native bridge to the Google Fit Android API, which Google has deprecated in favour of Health Connect. npm, license MIT.

Capacitor and Cordova

  • capacitor-health — A Capacitor plugin over both Apple Health and Health Connect, derived in part from cordova-plugin-health. npm, license MIT.
  • @capgo/capacitor-health — Capgo's Capacitor plugin over HealthKit and Health Connect — the other cross-platform choice for Capacitor apps. npm, license MPL-2.0.
  • @perfood/capacitor-healthkit — An iOS-only Capacitor plugin for HealthKit, still found in older Ionic projects. npm, license MIT.
  • cordova-plugin-health — The Cordova plugin over HealthKit and Health Connect, published since 2016 and documented for manual use under Capacitor. npm, license MIT.

Flutter

  • health — The Flutter plugin over HealthKit and Health Connect most Flutter health apps start from. pub.dev, license MIT.
  • health_connector — A newer Flutter SDK over HealthKit and Health Connect, first published in November 2025 — the alternative to `health`. pub.dev, license MIT.
  • health_kit_reporter — An iOS-only Flutter wrapper around the HealthKitReporter CocoaPods library. pub.dev, license MIT.
  • flutter_health_connect — A Health Connect-only Flutter plugin that still turns up in search results and older projects. pub.dev, license MIT.

Python

  • garminconnect — The Python client most people reach for to read their own Garmin Connect data. PyPI, license MIT.
  • garth — The Garmin auth library garminconnect used to depend on; its README now declares it deprecated. PyPI, license MIT.
  • stravalib — The Python client for the Strava V3 API. PyPI, license Apache-2.0.
  • oura-ring — A Python client for the Oura API v2 with an OAuth2 helper. PyPI, license MIT.
  • oura — The older Python Oura client (repository python-ouraring), whose maintainer is asking for someone to take it over. PyPI, license MIT License.
  • fitbit — The python-fitbit client for the legacy Fitbit Web API, which Google is retiring in favour of the Google Health API. PyPI, license Apache 2.0.
  • withings-api — A Python client for the Withings Health API using OAuth 2.0. PyPI, license MIT.

MCP servers for health data

Model Context Protocol servers whose official MCP Registry entry names a health or fitness source, read from the registry on 2026-10-17. The description is the registry's, verbatim; none of these servers was reviewed or run for this list. Each links its repository, else its website, else its registry record.

Apple Health (HealthKit)

Health Connect

Google Health API

Fitbit

Samsung Health

Garmin

Oura

WHOOP

Polar

Withings

Suunto

Dexcom

Strava

MyFitnessPal

Cronometer

Junction (formerly Vital)

Several sources

Wearable, fitness and health data in general

Open datasets

Datasets aifitnessapi.com publishes, each as JSON and CSV under the license it states, versioned rather than overwritten.

Free tools

Browser tools on aifitnessapi.com built on the same data. They run on your device and need no account.

  • Which error is this? — Paste an error string and get the matching HKError.Code case in Apple's wording, plus the guide that covers it.
  • Sum it or average it? — Whether Apple describes a quantity type as cumulative or discrete, with the sentence that says so.
  • Apple type, Android record — Two-way lookup between HealthKit identifiers and Health Connect records — verified pairs only.
  • HealthKit permission builder — Pick the types your app touches: the Info.plist keys, the toShare/toRead Swift, and the Health Connect record names.
  • HealthKit query generator — Pick a quantity type and a window; get the HKStatisticsQuery with the aggregation option Apple's own prose states.
  • Fitness app stack generator — Answer four questions and get the HealthKit types and APIs that survive them, with the exclusions shown.
  • Synthetic health data generator — Seeded synthetic HealthKit, Health Connect and Google Health API fixtures as JSON or CSV, with per-record UTC offsets.
  • Is this webhook real? — Paste an Oura, WHOOP, Terra, Polar, Strava, Withings, Wahoo or Google Health API webhook: the vendor's documented check, run in your browser.
  • Wearable OAuth playground — Pick Oura, WHOOP, Strava, Polar, Withings, Wahoo, Dexcom, Suunto or Google Health: documented endpoints and scopes, an authorize URL, a PKCE pair and token curl. Sends nothing.
  • Starter scaffold generator — Pick Express, Next.js or FastAPI and Oura, WHOOP, Polar, Strava or Wahoo: a tested project skeleton with OAuth routes, a token store and verified webhooks, as a .zip.
  • Pose keypoint playground — Click a joint and see its index in BlazePose, COCO, OpenPose, ML Kit and Apple Vision, then copy an index map built from matching names only.
  • Exercise form rules — The joint-angle thresholds open-source exercise trackers use for squats, push-ups, lunges, planks, curls and presses, each quoted from its code; null where none says.
  • Exercise taxonomy crosswalk — free-exercise-db, wger and ExerciseDB v1 categories, equipment and muscles against HealthKit and Health Connect workout types, matched by name only.
  • Health data schema converter — Paste a HealthKit export row, Health Connect record or Google Health API data point and see it in one unified schema, each field traced to its source.
  • Fitbit to Google Health API map — Search every Fitbit Web API endpoint and see its Google Health API data type, method and scopes from Google's migration tables, or that none is listed.
  • Deprecation scanner — Paste code or a manifest and find Fitbit Web API, Google Fit and other retired fitness API calls, each with its replacement. Also a GitHub Action.
  • Fitness app build plan and PRD generator — Pick an app type, platforms, data sources and features: a shareable build plan and a PRD template with the APIs, compliance items, store rules and cost shape.
  • App Store and Google Play submission checklist — Apple's App Review Guidelines and Google Play's health policies, quoted item by item and narrowed to what your app does, with progress kept in your browser.
  • Health app compliance wizard — Nine questions route your app to the rules that likely apply (HIPAA, the FTC breach rule, GDPR, Washington, FDA, app stores), each quoted from its source.
  • Which fitness API should I use? — Three questions, a tailored recommendation.
  • Fitness API cost planner — The cost structure of your stack: billing models, user-side costs, approval gates, eng effort.
  • Fitness & health API market map — Every product in the directory as one map, grouped by category, filterable by billing model, approval gate and tracked library.
  • Fitness API index — Sortable raw signals per product: SDK and library releases, dated changes in the last 12 months, approval gates, verification age. No score.
  • Fitness API openness index — Which developer basics each wearable and health-data API documents: self-serve start, sandbox, pricing, rate limits, signed webhooks, PKCE, refresh, deletion.
  • Compare two fitness APIs side by side — Access structure, user-side cost and approval gates for any two products in the directory.
  • Wearable API coverage matrix — Which wearable and fitness APIs document which metrics, at what resolution, how far back, and by webhook or pull. Every mark sourced; unknown where no page says.
  • Rate-limit and quota calculator — Users × syncs × endpoints against each fitness API's documented rate limits: which binds first, the most users it supports, and the vendor's own mitigations.
  • Why “today’s steps” is a bug — Interactive: DST days aren't 24 hours, so a fixed UTC window drops or double-counts an hour.
  • Ship It: a fitness-app survival game — Pick a product and a data stack, then live through the real, dated API events that hit it: Fitbit turn-off, Google Fit end of support, Garmin approval, Strava rules.
  • Pose model benchmark — Time MediaPipe Pose Landmarker lite, full and heavy on your own device, copy the latency table as markdown and submit it to the leaderboard.
  • Rep counter playground — Load a workout video, see joint angles over time, tune a hysteresis rep counter's thresholds and export the config as JSON. The video stays in your browser.
  • Bluetooth heart-rate lab — Connect a BLE heart-rate strap in the browser: every 0x2A37 byte decoded, and whether it sends the RR intervals HRV needs.
  • FTMS lab — Connect a treadmill, indoor bike, rower or cross trainer over Web Bluetooth, or paste hex: every FTMS flag bit and field decoded against the SIG structure.
  • Cycling power and cadence lab — Cycling Power (0x2A63) and CSC (0x2A5B) decoded, with cadence and speed computed from cumulative revolutions and event times, live or pasted.
  • BLE GATT explorer — Connect any Bluetooth LE device: services and characteristics by SIG name, read or notify, values decoded where the SIG defines a structure.
  • Which wearable API quiz — Eight questions on platform, devices, data depth, webhooks, budget and team decide how your app should get wearable data, with a shareable result.
  • My stack — Pick the APIs your product depends on: their tracked changes and deadlines, every page here about them with its date, and a calendar to save. Stays in your browser.
  • Answer search — Search the full text of every answer capsule, FAQ answer and tracked change, ranked in your browser, with links to the exact answer.
  • Daily health-API developer puzzle — Five questions a day from the site's datasets: which platform throws this error, HealthKit to Health Connect, sum or average, name the keypoint.
  • Step lab — Walk with your phone and watch a visible step detector count; move its threshold and interval to see why two apps disagree.
  • Apple Health export explorer — Open your iPhone Health export.zip in the browser: record types with counts and dates, sources, a daily chart and a CSV per type. Nothing is uploaded.
  • Gym software API matrix — Mindbody, Glofox, TeamUp, Mariana Tek, Wodify and more: auth, access, pricing, webhooks and coverage, filterable, each cell quoting its vendor source.
  • Research platform chooser — Fitabase, Labfront, Empatica and Ametris: tick what your study needs and see which platforms document it, each answer quoting the vendor's page.
  • Health data aggregator chooser — Terra, ROOK, Junction, Spike, Thryve, Sahha, Open Wearables and Validic: tick sources, price, webhooks, BAA, data region or self-hosting; every cell quotes its source.

How the list is made

  • Generated by scripts/build-awesome.mjs into AWESOME.md at the root of this site's public repository, and rendered here from the same function, so the file on GitHub and this page list the same entries. A qa gate fails the build when the file is stale.
  • API lines restate the directory: category, how the product bills developers, and whether its entry names an approval step before production. Library lines are the libraries hub's own one-line notes with the registry's license; MCP server lines are the official MCP Registry's descriptions, verbatim and not reviewed.
  • Inclusion is mechanical and nothing is ranked: every directory product, every library on the hub, every server the registry scan matched, every published dataset and tool.
  • KinesteX funds this site. Its line is drawn from the same directory fields as every other product's.

Free to copy and share under CC BY 4.0: credit AIFitnessAPI and link https://aifitnessapi.com/awesome. Found a wrong line? It is wrong in the data, so report it and the list regenerates.