GCX-GCD practice question 9 of 15

Which of the following endpoints are in the list of conversation endpoints? (Choose four.)

Choose your answer, then check it against the explanation and the full breakdown below.

Answer options

Correct Answer:

A, B, D, E

Explanation

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.

Why Incorrect

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.

References

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

Question 9 of 15

Question breakdown

Tests: Identify Conversations API endpoint structure
Difficulty: Medium

Key idea: The Conversations API offers top-level list endpoints per media type, while participants and attributes are sub-resources of a specific conversation.

How to reach the answer

Look for endpoints that list conversations by media type: callbacks, calls, chats, messages.
Each of these exists as GET /api/v2/conversations/{mediaType} and returns the caller's active conversations of that type.
Participants are always reached under /conversations/{conversationId}/participants, not at the top level.
Attributes belong to a participant inside a conversation, so a top-level attributes endpoint does not exist.

Each option

ACorrect. GET /api/v2/conversations/callbacks lists callback conversations.
BCorrect. GET /api/v2/conversations/calls lists call conversations.
CIncorrect. Participants require a conversationId in the path; there is no top-level participants list.
DCorrect. GET /api/v2/conversations/chats lists chat conversations.
ECorrect. GET /api/v2/conversations/messages lists message conversations.
FIncorrect. Attributes are updated on a participant within a conversation, not queried from a top-level endpoint.

Common trap: Participants is a real concept in the API, so a top-level participants path looks plausible even though it must be scoped to a conversation.

In practice: Developers building agent tools call the media-specific list endpoints to find active interactions, then drill into a conversationId to manage participants or set attributes.

Remember: Media types are top-level under /conversations; participants and attributes need a conversationId.

Official documentation: Genesys Cloud API Explorer

Drafted with AI assistance and checked against the answer key.

Keep practicing

Take the free GCX-GCD practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test