Fitness APIs in 2026, so far
10 numbers about the fitness and health API ecosystem, one per slide, each computed from this site's own data files at the build of November 9, 2026. It becomes the full-year recap on the first build of 2027.
How the story is computed
Every slide is produced by src/lib/year2026.ts from modules the repository already holds, at build time, with no generator of its own. A change counts in 2026 when its tracker date, at the precision its source states, falls in 2026; undated watch items are excluded. A release counts once per package and version, whichever file holds it. A slide whose number would rest on one item is dropped instead of shown.
Two limits are stated on the slides they affect. sdkReleases.ts keeps each repository's five newest GitHub releases, so a count that fills all five is a floor. libraries.ts keeps only each package's latest registry publish, so it says whether a package released in 2026, never how often. The freshness slide reads the updated stamp of every cluster page, with ages counted in whole days between UTC midnights, the same arithmetic as the site's own staleness flags.
Frequently asked questions
How is the Fitness APIs in 2026 story different from the changes tracker and the State of Fitness APIs report?
It counts; they explain. The changes tracker is the record of every dated change, each with the vendor's words and a confirmed-or-reported grade, and the State of Fitness APIs 2026 report surveys how access to 25 APIs is structured. This page adds up the year: how many tracked changes, which month was busiest, how many releases are on file, how fresh this site's own checks are. Each number links to the page that owns the detail behind it, and none of the report's findings is repeated here.
Where do the numbers in the 2026 story come from?
Only from data files already in this site's repository, read at build time: src/data/changes.ts for the tracked changes, src/data/googleHealthApi.ts for the Google Health API launch and the Fitbit turn-off date, src/data/hcReleases.ts, sdkReleases.ts and libraries.ts for releases, and the updated stamp on every cluster page for freshness. Every slide names its file and the date that file was last read from its source. Nothing is typed in by hand, and a slide whose number would rest on a single item is left out.
Why does the 2026 story say "so far", and when does it become a full-year recap?
The title is computed from the build date. Every build before January 1, 2027 calls the page "so far"; the first build after that date titles it as the year in numbers, with the same code and no edit. Release counts also stop at the date each data file was last read, which every slide states.
Why are some 2026 changes in the story not placed in any month?
Because their sources do not give one. The tracker keeps a date at the precision its evidence states, and several 2026 entries are dated only by year. They count toward the year's total and appear in their own column on the month chart, but placing them in a month would sharpen a date beyond what the source says.
Keep reading
By AIFitnessAPI. Cite as: AIFitnessAPI, "Fitness APIs in 2026, so far," https://aifitnessapi.com/2026, as of November 9, 2026. Product and company names are trademarks of their respective owners.