Conversation Tags
7 endpoints served by the ConversationTagResourceController 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.
The controller is mounted at 2 base paths; both serve the same handlers:
/core2/tnt/dm/alg/cc/conversation-tag/core2/tnt/dm/alg/cc/conversation-tags
Endpoints
| Method | Path | Handler | Request body | Source |
|---|---|---|---|---|
POST | /core2/tnt/dm/alg/cc/conversation-tag | create | ConversationTagContainer | ConversationTagResourceController.java:58 |
PUT | /core2/tnt/dm/alg/cc/conversation-tag | update | ConversationTagContainer | ConversationTagResourceController.java:90 |
GET | /core2/tnt/dm/alg/cc/conversation-tag/distinct/pagination | getListDistinctPagination | — | ConversationTagResourceController.java:286 |
GET | /core2/tnt/dm/alg/cc/conversation-tag/{uuid} | get | — | ConversationTagResourceController.java:153 |
DELETE | /core2/tnt/dm/alg/cc/conversation-tag/{uuid} | delete | — | ConversationTagResourceController.java:184 |
GET | /core2/tnt/dm/alg/cc/conversation-tags | getList | — | ConversationTagResourceController.java:216 |
GET | /core2/tnt/dm/alg/cc/conversation-tags/pagination | getListPagination | — | ConversationTagResourceController.java:254 |
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
- Unified Contact Center API — the other controllers in this family
- API Reference — how many endpoints exist per family, and which have a page
Last updated on