API versioning
Understand the current v1 path strategy and compatibility model.
The API version is part of every public path:
https://api.godaily.co.il/v1Only v1 exists. The documentation therefore shows a version indicator, not a selector.
Compatibility within v1
Integrations should tolerate additive changes such as new nullable response fields, new enum values where the schema permits them, and new endpoints. Ignore unknown object properties and avoid exhaustive parsing that crashes on a value it does not recognize.
A change that removes or repurposes a documented field, changes its fundamental type, changes an existing route's meaning, or requires incompatible client behavior would require an explicit versioning and communication decision. This documentation does not promise a deprecation timeline that Daily has not established.
Monitor the changelog and the committed OpenAPI version in your integration review process. Pin generated clients to a reviewed OpenAPI artifact and update deliberately.