In Genesys Cloud CX, when scheduling a callback via aPOSTrequest to/api/v2/conversations/callbacks, you can specify eitherqueueIdorroutingData:
queueId:This parameter is used for basic routing, directing the callback to a specific queue by its unique identifier. It facilitates straightforward ACD (Automatic Call Distribution) routing without additional routing attributes.

routingData:This parameter allows for more advanced routing configurations. It enables the inclusion of additional routing attributes such as skills, languages, or other criteria, providing greater control over how the callback is routed within the system.

When making the initialGETrequest tohttps://api/v2/conversations/{conversationId}/recordings, if the recording is not yet available (e.g., it's still being transcoded), the API responds with a 202Accepted status code and an empty response body, meaning themediaUriis not included in this response. Once the recording becomes available, subsequent requests will return a 200OK status code along with themediaUriin the JSON response body, allowing access to the recording.

Genesys Cloud CX provides Platform Recording APIs that enable users to download recordings programmatically. This allows for efficient retrieval and management of recorded interactions.
Genesys Cloud CX supports integrations with cloud storage services, such as AWS S3, allowing organizations to store recordings externally. This facilitates bulk downloading and long-term storage of recordings.

In Genesys Cloud CX, widget permissions are not assigned to individual users. Instead, permissions related to web chat widgets are managed through roles and permissions within the platform. To create or manage web chat widgets, a user must have the appropriate permissions, such as Widgets > Deployment > AllorWeb Chat
> Deployment > All.These permissions are typically assigned to administrative roles responsible for configuring and deploying web chat functionalities.
Reference:https://help.mypurecloud.com/articles/create-a-widget-for-web-chat/

Genesys Cloud CX operates in separate regional environments (e.g., North America, EMEA, APAC). OAuth clients are region-specific, meaning an OAuth client created for North America won't authenticate users in Europe. To resolve this, a new OAuth client must be created in the European region's environment.