Are Fitness APIs Free? An Honest Overview

The three kinds of "free"#

Before the categories, fix the vocabulary, because it settles most arguments:

• Free to call — you register a developer app and hit the API with no per-request fee to the provider. Fitbit, Oura, and WHOOP work this way.
• User-side cost — the data only exists if your end user owns the device and, increasingly, pays a membership (Oura Membership, WHOOP subscription). For you the developer this is $0; for your product it caps who can actually connect.
• Your-side cost — servers, storage of high-volume wearable history, OAuth token refresh, webhook handling, monitoring, and the engineering time to survive approval queues and API migrations. This is real money even when the API sticker says free.

A "free to call" API can still be expensive to ship. Keep these three columns separate on every vendor you evaluate.

Are fitness APIs free? By category#

Fitness APIs are not one market. They split into four buckets that price completely differently.

First-party wearable APIs: free to call, but gated#

Fitbit's Web API has historically been free to call, Oura's API FAQ says the Oura API is free to use for both personal and commercial applications, and WHOOP's API Terms of Use, effective October 6, 2026, say access is currently provided at no charge. What gates them is not a usage bill but approval and membership. Oura limits a new API application to 10 users until Oura approves it; WHOOP requires developers to hold a WHOOP membership to build at all, and a new app starts on a Sandbox tier of 10 members, moving up one tier at a time through WHOOP's review; Fitbit is mid-migration to the Google Health API during 2026, and the successor's pricing model is not clearly public yet — verify. Note the Google Health API is a different product from the paid Google Cloud Healthcare API, so don't read the latter's per-request pricing as the former's.

Strava and Garmin: free to call, with extra conditions#

Two more providers charge nothing for API access but add conditions of their own, so don't blanket-state that all wearable APIs are free to use. Strava's API Agreement, effective June 1, 2026, says access to its API is currently provided at no charge, but its getting-started guide calls a Strava subscription a prerequisite for creating an app, and its API Policy makes Standard Tier apps subject to subscription requirements for the developer or specified end users. Garmin's program FAQ said, until its October 2026 reorganisation, that there were no licensing or maintenance fees for access to the Garmin Connect Developer Program. Read on October 22, 2026, Garmin's pages state no price for Starter Access, say Enterprise options and commercial terms are tailored to business and technical requirements, and mark features such as ping/pull delivery and enhanced beat-to-beat interval as Enterprise-only; get terms in writing.

Aggregators: genuinely paid#

If you want one integration across many devices instead of building each provider yourself, aggregators like Terra, Junction (formerly Vital), Rook, and Spike are where recurring API spend actually accrues. The model is consistent even where the numbers aren't public: you pay per connected user or per MAU, tiered by user count, often with a credit/event layer and an enterprise "contact sales" top tier. Specific per-user dollar rates are rarely listed publicly — verify with the vendor. This is the classic build-vs-buy trade: a real recurring fee in exchange for skipping N separate first-party integrations.

Nutrition and exercise content: mixed, with real free options#

Content APIs are the most varied bucket. The commercial ones are freemium or tiered — Nutritionix, Edamam, and Spoonacular for nutrition; ExerciseDB (now sold by AscendAPI) and API Ninjas for exercises — typically a limited free tier that scales into paid plans by volume or features, with metered overages. But genuinely free and open options exist and are worth naming plainly: USDA FoodData Central (public domain, free API key), Open Food Facts (open, no key, ODbL attribution), wger (AGPL, self-host), and free-exercise-db (public domain, static dataset). These cost $0 for the data but shift integration, hosting, and license-compliance work onto you.

The catch: what to budget for even when it's free#

The provider's price tag is usually the smallest number. What actually adds up:

• User membership dependency — if your product relies on Oura or WHOOP data, your addressable market is only users already paying that provider. Free for you, but it shrinks who can connect.
• Approval and time-to-market — Garmin's application review, Oura's approval for apps past 10 users, and WHOOP's reviewed member tiers cost calendar time, which is a real cost for a roadmap even at $0.
• Maintenance and migrations — APIs deprecate and move. Fitbit's 2026 shift to the Google Health API forces a re-integration; Strava's 2024–2026 changes altered display rules and access economics. Budget engineering time for this every year.
• Your infrastructure and storage — wearable data is continuous and high-volume; storing and re-syncing history is an ongoing bill.
• License obligations — the "free" open datasets carry terms: public domain has none, ODbL adds attribution/share-alike, AGPL adds copyleft. These can force architecture or legal work, not just payment.
• Compliance — health data carries privacy and security obligations (consent, deletion, sometimes HIPAA-adjacent scope) regardless of API price.

Free to license, expensive to integrate#

The licence price and the engineering bill often run in opposite directions. When we counted this site's API directory on October 18, 2026, 14 of its 24 products carried a developer cost of free, and five of those were also rated high engineering effort, which is our rough judgement rather than a vendor fact: wger, MediaPipe, MoveNet, Apple Vision body pose and Garmin. That is every product in the directory rated high effort. Money buys you someone else's engineering time, and declining to spend it means spending your own.

Three of the five are pose models, where the cost moves from the invoice to the device: frame handling, thermal limits, battery, and an accuracy question that only real users on real hardware can answer. Of the five, only Garmin states an approval gate, a request it has to approve before you get its Developer Portal, so most of the hardest integrations in the free group are ones you can start this afternoon, which is why teams underestimate them. Our build versus buy guide for motion tracking walks that trade.

Cheaper paths and how it compares#

Which path is cheapest depends on your shape. Few devices, willing to do approvals, engineering to spare → direct first-party APIs (near-zero API fee, high integration and maintenance cost). Many devices, want one integration and a predictable per-MAU budget → an aggregator (real recurring fee, less maintenance). Most teams end up mixing. If you only need workout or food content rather than a specific person's wearable history, the genuinely free and open options often cover it. For the full roundup of no-cost and open choices, see the free fitness APIs roundup — this page won't reproduce it. To compare the landscape and decide which provider fits, see the fitness API hub, and for a structured breakdown of what a build actually runs, see how much a fitness API costs.

The honest close#

So, are fitness APIs free? Many are free to call — most first-party wearable APIs charge no per-request fee — and a few nutrition and exercise datasets are genuinely free and open. But Strava requires a Strava subscription to create an app, Garmin publishes no price for Starter Access and tailors Enterprise terms, aggregators are paid by design, and the costs that actually bite (user memberships, approval time, maintenance, your own infrastructure) sit outside the API sticker. Pricing and access rules for this category changed noticeably in 2026 and vary by country, so verify every specific against the provider's live docs — or a sales conversation — before you build a budget on it.