Changelog
Explore the iterative history of the Health Fitness API. Every endpoint shipped, metric added, and architectural enhancement — chronologically mapped for full transparency with our developer community.
v1.0.0 Major Release
March 5, 2026
Major release — 35 new advanced fitness intelligence endpoints, new direct enterprise platform at `api.hefitapi.com`, native multi-language support (8 languages), structured actionable responses with risk scores and recommendations. Transforms the API into a full-stack fitness intelligence infrastructure.
New (35)
Fixes (3)
Deprecated (0)
No deprecations in this release.
v0.0.4 Expanded Feature Set
May 27, 2025
16 new endpoints across cardiovascular diagnostics, metabolic calculations, nutrition/macronutrients, and diet/lifestyle tools. Focus on clinical and diagnostic calculators for health platforms.
New (16)
Fixes (0)
No fixes in this release.
Deprecated (0)
No deprecations in this release.
v0.0.3 Expanded Feature Set
March 2025
17 new endpoints covering body composition indexes, cardiovascular risk assessment, metabolic health markers, and unit conversions. Added GET & POST support across the board.
New (17)
Fixes (3)
Deprecated (0)
No deprecations in this release.
v0.0.2 Expanded Feature Set
Early 2025
8 new endpoints covering military body fat standards, energy expenditure calculations, and micronutrient requirements.
New (8)
Fixes (0)
No fixes in this release.
Deprecated (0)
No deprecations in this release.
v0.0.1 Initial Release
Late 2024 / Early 2025
Foundational launch — core body composition, metabolism, hydration, and fitness benchmark endpoints. Establishes the baseline health and fitness API toolkit.
New (13)
Fixes (0)
Initial release — baseline launch.
Deprecated (0)
No deprecations in this release.
Changelog FAQs
How often is the Health Fitness API updated?
We release updates based on community feedback, new endpoint research, and infrastructure improvements. Major releases introduce new fitness intelligence modalities and endpoint expansions, while minor patches focus on stability and performance.
How do I get the latest version?
If you're using the API through api.hefitapi.com, you're always on the latest version — updates are deployed server-side with zero downtime. No client-side changes are needed.
Are older endpoint versions still available?
Yes. We maintain backward compatibility for standard health and fitness calculations. New interpretations, expanded metrics, and additional endpoints are additive and won't break existing integrations.
How can I contribute a feature request or report a bug?
Open an issue on our GitHub or reach out through our contact page. We welcome community input on endpoint behavior and metric accuracy.
What does the version numbering mean?
We follow semantic versioning conventions. Major version bumps (1.0.0) indicate significant platform expansions. Minor versions (0.x.0) cover endpoint additions. Patch versions (0.0.x) cover fixes and performance improvements.
Are migration guides provided for breaking changes?
Yes. When a release introduces changes that affect existing integrations, migration guidance is included in the release notes and linked from the documentation.
What is the deprecation policy for endpoints?
Endpoints are not removed without advance notice. Deprecation announcements appear in the changelog and documentation well before any removal takes effect.
Can I subscribe to release notifications?
Yes. Follow us on X (@dakidarts) or check this changelog page regularly for the latest updates. Enterprise customers receive direct release notifications.