Fitness API research
3 studies · newest data read Nov 6, 2026
The studies
How often fitness API documentation changes under us
From the git history of this site's quoted evidence: how often fitness and health API vendor pages changed under our quotes, per host. Dataset included.
- 28
- source changes under this site's quotes, counted once per host per commit, on 21 hosts
- 635 of 7,984
- evidence rows replaced because their source changed
History read through Nov 5, 2026 (main at 8fb512e)
Read the study →How much notice fitness API shutdowns gave
Days from announcement to end date for each shut-down or deprecated fitness API in the graveyard where both dates are sourced, with exclusions and data.
- 3 of 15
- graveyard entries with a dated vendor announcement and an end date to the day
- 92 days
- median notice between announcement and end
Announcement pages read Nov 6, 2026
Read the study →Which fitness API vendors publish their prices
Per vendor: published price, no published price or free, each with the vendor's own line as quoted in this site's evidence. Counts by category and data.
- 14 of 25
- vendors publish a price for a paid developer plan
- 5 of 25
- name a paid plan or commercial terms with no price
Pricing pages reviewed Oct 17, 2026 to Nov 5, 2026
Read the study →
How these are made
Each study is computed by a script from files in this site's repository: the git history of its evidence files, the graveyard and the changes tracker, and the vendor lines its pricing pages quote. The rows are published as an open dataset before any figure is drawn from them.
The pages compute their figures from those rows at every build, and the site's quality checks recompute the headline figures from the published files and fail the build if the two differ. Each study states what its method cannot see.
Other numbers on this site
- Press numbers: counts of what this site tracks, each with its source file and date
- The State of Fitness APIs 2026: original research on 25 fitness APIs, SDKs and models: how they bill developers, approval gates and terms
- Fitness APIs in 2026: the year's tracked changes and releases, one figure at a time
- Open datasets: every dataset this site publishes, these three included
Frequently asked questions
Where does this site's original research come from?
From files in its own repository: the git history of the evidence files that hold every quoted vendor line, the Fitness API Graveyard and changes tracker, and the pricing pages' evidence. No survey, panel or third-party dataset is used.
Can I reuse the research figures and data?
Yes. Each study's rows are an open dataset under CC BY 4.0, in JSON and CSV with a card describing every column. Quote a figure with the date its data was read and link the study page, which carries a plain-text and BibTeX citation.
How are the research figures kept from going stale or wrong?
They are not typed by hand. The pages compute them from the published rows at each build, and the build fails if a headline figure differs from what the published file gives. Regenerating the rows is one script; the dates each study states say how old its data is.