Skip to content

Conversation Events

20 endpoints served by the ConversationEventController controller under the Unified Contact Center family. Every path here is resolved from the controller’s mapping annotations at the commit named in the front matter; the table lists what the backend serves and nothing else.

Access endpoints present: backoffice-ep, etl-ep. The segment decides how the caller authenticates — see Authentication and the Data API reference for the credential each one takes, the request headers, and the response envelope. Paths without an access segment take the signed-in user’s token.

Endpoints

MethodPathHandlerRequest bodySource
GET/core2/tnt/dm/alg/cc/conversation-eventsgetAllConversationEvent—ConversationEventController.java:158
POST/core2/tnt/dm/alg/cc/conversation-eventscreateConversationEventConversationEventContainerConversationEventController.java:79
PUT/core2/tnt/dm/alg/cc/conversation-eventsupdateConversationEventConversationEventContainerConversationEventController.java:104
GET/core2/tnt/dm/alg/cc/conversation-events/backoffice-epgetAllConversationEventBackoffice—ConversationEventController.java:354
POST/core2/tnt/dm/alg/cc/conversation-events/backoffice-epcreateConversationEventBackofficeEPConversationEventContainerConversationEventController.java:231
PUT/core2/tnt/dm/alg/cc/conversation-events/backoffice-epupdateConversationEventBackOfficeEpConversationEventContainerConversationEventController.java:273
GET/core2/tnt/dm/alg/cc/conversation-events/backoffice-ep/export/csvgetExportCsvBackoffice—ConversationEventController.java:465
GET/core2/tnt/dm/alg/cc/conversation-events/backoffice-ep/querygetConversationEventByCriteriaBackoffice—ConversationEventController.java:425
GET/core2/tnt/dm/alg/cc/conversation-events/backoffice-ep/{guid}getConversationEventByGuidBackoffice—ConversationEventController.java:390
DELETE/core2/tnt/dm/alg/cc/conversation-events/backoffice-ep/{guid}deleteConversationEventBackoffice—ConversationEventController.java:312
GET/core2/tnt/dm/alg/cc/conversation-events/etl-epgetAllConversationEventEtl—ConversationEventController.java:362
POST/core2/tnt/dm/alg/cc/conversation-events/etl-epcreateConversationEventEtlConversationEventContainerConversationEventController.java:241
PUT/core2/tnt/dm/alg/cc/conversation-events/etl-epupdateConversationEventEtlEpConversationEventContainerConversationEventController.java:281
GET/core2/tnt/dm/alg/cc/conversation-events/etl-ep/export/csvgetExportCsvEtl—ConversationEventController.java:473
GET/core2/tnt/dm/alg/cc/conversation-events/etl-ep/querygetConversationEventByCriteriaEtl—ConversationEventController.java:434
GET/core2/tnt/dm/alg/cc/conversation-events/etl-ep/{guid}getConversationEventByGuidEtl—ConversationEventController.java:399
DELETE/core2/tnt/dm/alg/cc/conversation-events/etl-ep/{guid}deleteConversationEventEtl—ConversationEventController.java:321
GET/core2/tnt/dm/alg/cc/conversation-events/querygetConversationEventByCriteria—ConversationEventController.java:203
GET/core2/tnt/dm/alg/cc/conversation-events/{guid}getConversationEventByGuid—ConversationEventController.java:181
DELETE/core2/tnt/dm/alg/cc/conversation-events/{guid}deleteConversationEvent—ConversationEventController.java:131

Path variables are shown as {name}. Request body is the declared @RequestBody type; the JSON shape of a container is the record it wraps, and the reliable way to learn it is to read one back with a GET before you POST one (the Data API reference explains the technique). Query endpoints (…/query) take the paging parameters described there.

Related

Last updated on