XKOVA Docs
Changelog
Release notes for the XKOVA API. Each entry records what changed in the public surface, so you can tell at a glance whether an upgrade needs work on your side. Breaking changes never land quietly here.
Current release
| Version | Status | Notes |
|---|---|---|
1.0.0 |
Pre-launch | Initial pilot API surface. Not yet generally available. |
The API path prefix is /v1/. See Versioning for what that
prefix promises and when a new major would appear.
How to read an entry
Every release entry groups its changes under fixed headings so you can scan for the parts that affect you. An entry that adds capability without removing anything carries an empty Changed, Deprecated, and Migration notes section, which is the signal that no action is required.
| Heading | What it lists |
|---|---|
| Added | New endpoints and new webhook events, each with a short purpose. |
| Changed | Behavior changes. A breaking change here is rare and is called out as such. |
| Deprecated | Surfaces scheduled for removal, with their sunset date. See Deprecations. |
| Fixed | Corrected behavior in existing surfaces. |
| Security | Security relevant changes. |
| Migration notes | What you must do to adopt the release, or a clear statement that nothing is required. |
Entry format
Future entries follow this shape. The version line carries the semantic version and the release date.
## v1.1.0 - 2026-06-15
### Added
- New endpoint: GET /v1/example - short purpose.
- New webhook event: example.created - short purpose.
### Changed
- (nothing breaking)
### Deprecated
- (none)
### Fixed
- A corrected field now populates reliably.
### Security
- (none)
### Migration notes
- No action required.Related
See Versioning for the compatibility policy, and Deprecations for how a surface is retired with notice.