Developers
API versioning
Lifecycle rules a caller can rely on are the ones the API reference states for each operation. This page does not add a hidden version.
What you do here
Prefer the documented operation over a path you discovered. Retirements, where the reference states them, are part of the contract.
What this does not grant
No separate version header, sunset calendar or beta channel is published beyond the reference.
Before you continue
Pinning a deployment you operate is your change control. It does not freeze RJV's public site.
Last reviewed 8 November 2026.