3.18.4 API Versioning
Beginning with this release, all REST APIs will be versioned in accordance with the standard practices adopted across Oracle Banking Products.
How API Versioning will Work
Consistent Versioning: APIs will now include clear version numbers. New versions will be introduced only when changes are not backward compatible.
Planned Support and Sunsetting: Existing API versions will remain supported for two product releases following the introduction of a new version, ensuring ample time for transition. Older versions will be retired (sunset) according to a predictable and transparent schedule.
Standardized Naming: API version labeling and access methods are being standardized. For example: Service APIs use /service/v<version>
Why this Matters
This approach ensures that API changes are transparent and predictable, reducing disruption to your development activities. You will receive advance notice before any API version is retired, along with clear guidance on migration paths.
What APIs are Available in the Patch Set?
- All non-versioned APIs and non-standard versioned APIs available up to Release 14.8.0.0.0 will remain supported in the current release. However, these APIs will be sunset in the next Patch Set Release.
- Versioned APIs, which serve as alternatives to the non-standard APIs, are now available and should be adopted by customers going forward.
Sunset APIs
NIL
Parent topic: Web Services