Are Fitness APIs Free? An Honest Overview

Are fitness APIs free? The honest answer is: many are — but "free" hides three different meanings, and confusing them is how teams blow a budget. The single most useful distinction is between an API that is free to call (no per-request fee paid to the provider), a cost the user carries (they must own the device or hold a membership for their data to exist), and your own cost (infrastructure, storage, approval time). Most first-party wearable APIs — Fitbit, Oura, WHOOP — are free to call. Aggregators are genuinely paid. Nutrition and exercise content APIs are mixed, and a handful are truly free and open. Every specific figure below is volatile as of 2026 — verify current pricing on the provider's own page before you plan around it.

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 Cloud API lists no developer fee, and WHOOP's developer platform has no documented per-call charge. What gates them is not a usage bill but approval and membership. Oura caps a freshly registered app at roughly 10 connected users until you pass its review; WHOOP requires developers to hold a WHOOP membership to build at all; 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.

The first-party exceptions

Two providers break the "free to call" pattern, so don't blanket-state that all wearable APIs are free. Strava reportedly now requires Standard-tier developers to hold a paid Strava subscription (the normal membership, around $11.99/mo in the US and varying by country — verify), effective in mid-2026. Garmin does not publicly list its Health API terms at all; access is partner-approval-only, and third parties report a setup fee and possible commercial licensing that could not be confirmed on a Garmin-owned page — treat as unverified and do not label Garmin "free."

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 (via RapidAPI) 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 partner review, Oura's partner tier, and WHOOP's gating 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.

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 /fitness-apis/free-fitness-apis — this page won't reproduce it. To compare the landscape and decide which provider fits, see /fitness-apis, and for a structured breakdown of what a build actually runs, see /pricing/how-much-does-a-fitness-api-cost.

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 and Garmin break the pattern, 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.