The Genesys Cloud CX Platform API organizes conversation data by media type. The API provides distinct endpoints to list conversations for specific channels. The endpoints GET /api/v2/conversations/callbacks, GET /api/v2/conversations/calls, GET /api/v2/conversations/chats, and GET /api/v2/conversations/messages are all valid methods for retrieving lists of active conversations, filtered by their respective media type. These are fundamental endpoints within the Conversations API for interaction management and reporting.

C. GET /api/v2/conversations/participants is not a valid top-level endpoint. Participants are a sub-resource of a specific conversation, accessed via /api/v2/conversations/{conversationId}/participants.

F. GET /api/v2/conversations/attributes is not a valid endpoint. Attributes are properties of a participant within a specific conversation, not a top-level queryable resource.

1. Genesys Cloud CX Developer Center, API Reference, Conversations API. The documentation lists the following valid endpoints for retrieving conversations by media type:

GET /api/v2/conversations/calls - Get a list of calls.

GET /api/v2/conversations/chats - Get a list of chats.

GET /api/v2/conversations/callbacks - Get a list of callbacks.

GET /api/v2/conversations/messages - Get a list of messages.

Source: developer.genesys.cloud/api/rest/v2/conversations/#get-api-v2-conversations-calls (and respective pages for chats, callbacks, messages).

2. Genesys Cloud CX Developer Center, API Reference, Conversations API. The documentation for managing participants shows that they are always accessed within the context of a specific conversation ID ({conversationId}), confirming that GET /api/v2/conversations/participants is not a valid structure.

Source: developer.genesys.cloud/api/rest/v2/conversations/#get-api-v2-conversations--conversationId--participants--participantId-

3. Genesys Cloud CX Developer Center, API Reference, Conversations API. Similarly, participant attributes are managed under a specific participant within a specific conversation, confirming GET /api/v2/conversations/attributes is not a valid endpoint.

Source: developer.genesys.cloud/api/rest/v2/conversations/#patch-api-v2-conversations--conversationId--participants--participantId--attributes