The purpose of the Genesys Cloud CX API Change Management Policy is to articulate the agreement between our customers, partners, and the Genesys…

The Genesys Cloud CX API Change Management Policy explicitly categorizes API modifications to ensure clarity and predictability for developers. The four official change types are: New feature (adding new APIs), Non-breaking (backward-compatible changes), Breaking (non-backward-compatible changes), and Deprecations (retiring APIs). These classifications govern the notification timelines and processes that Genesys follows, allowing customers and partners to manage their integrations effectively. This structured approach is fundamental to maintaining a stable and reliable API ecosystem.

A. Minor Bugs: Bug fixes are not a distinct change type; they are categorized as either "Non-breaking" or "Breaking" depending on the impact of the fix on existing API contracts.

E. Emergency: An emergency is a condition or scenario that may require an accelerated change process, particularly for breaking changes, but it is not a formal API change type itself.

1. Genesys Cloud CX Developer Center, "API Change Management," Section: Change Types. This official document lists and defines the four applicable change types: New feature, Non-breaking, Breaking, and Deprecations. It does not list "Minor Bugs" or "Emergency" as formal classifications.