LIVECT
Versioning
The production integration guide identifies the interface version used by each integration. Public examples may use versioned paths such as /v1, once the corresponding production contract is published.
✓Backward-compatible changes evolve within the current version.
✓Breaking changes require a new version or an agreed migration plan.
✓Deprecated behavior is documented in the enterprise integration guide.
✓The production endpoint and error contract are published only after stabilization.