As the Genesys Cloud CX product grows, additions are made to the API to support new features in the form of new resources, new HTTP methods for…

The statement accurately describes the Genesys Cloud CX API versioning and change management policy. The platform API is designed to be backward-compatible within a major version (e.g., v2). Additive changes, such as new resources or properties, are introduced without changing the version. However, to maintain stability for existing integrations, any necessary "breaking changes" (e.g., removing a property, changing a data type) are intentionally deferred and grouped into a future major version release. This ensures that applications built on the current API version will not break unexpectedly.

B. False: This is incorrect. The official Genesys Cloud CX Developer documentation explicitly states that breaking changes are deferred to the next major revision of the API whenever possible to avoid disrupting existing applications.

1. Genesys Cloud CX Developer Center, "API Versioning". The documentation states, "As the Genesys Cloud product grows, additions are made to the API to support new features... These changes are additive and are not considered breaking changes. When breaking changes are necessary, they are deferred to the next major revision of the API whenever possible." (developer.genesys.cloud/platform/api/versioning)

2. Genesys Cloud CX Developer Center, "Announcing API v2". This document illustrates the process of a major version change, stating, "API v2 was created to allow us to make breaking changes to the API." This supports the principle of bundling breaking changes into new major versions. (developer.genesys.cloud/blog/2016-08-26-announcing-api-v2/)