Versioning and Changes
BreakingBet API is constantly evolving, and to maintain backward compatibility, we apply API versioning.
How New Features Will Be Added
If a change does not affect backward compatibility (e.g., adding new fields), it can be introduced in the current version without requiring client updates.
Breaking Backward Compatibility
If a change breaks backward compatibility, the following procedure applies:
- A new API version is launched.
- The previous version continues to work for at least 2 months.
- During this time:
- both versions are available in parallel,
- users can migrate to the new version at their convenience.
After the support period expires, the old version may be discontinued.
Supporting Old Versions
During the parallel support period:
- documentation will be available for each version,
- Swagger UI will be tied to a specific API version,
- version behavior will not change without announcement.
How to Learn About Changes
Information about API changes will be published:
- in the documentation,
- through official BreakingBet communication channels.
Recommendation
It is recommended to follow updates and plan for API version updates in client code.