Breaking contract change
Reserved for intentional breaking changes to public request or response contracts and primary auth behavior.
Changelog
Versioning and partner-facing release discipline.
This page should be the public release record for partner integrations. Keep it explicit, concise, and tied to actual product behavior.
How partners should interpret change
Additive commercial release
Use for new partner-facing features and additive public capabilities that do not break existing integrations.
Fix or clarification
Use for bug fixes, clarifications, and operational improvements that preserve the public contract.
What should and should not move under partners
Public endpoint names
Keep the primary public endpoints stable within a major version.
Commercial species contract
Commercial v1 remains dog and cat only until a broader scope is explicitly released.
Additive response fields
Additive fields are acceptable in minor or patch releases if existing clients do not break.
Auth or required payload shifts
Changes to auth, required request fields, or primary response structures should be handled as major-version work.
Commercial release record
2.5.0
Commercial launch release for dog and cat workflows, including medication calculations, drug search, detailed drug records, and DailyMed label search.
Clinical workflows
Standard dosing, BSA-aware calculations, CRI workflows, and canine/feline fluid workflows are part of the production API.
Partner access
Trial onboarding, subscription-aware commercial access, and API-key lifecycle management are in place.
Species support
Commercial v1 supports dog and cat workflows only; broader species remain future scope.