Messages
11 endpoints served by the MessageResourceController 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/messages/core2/tnt/dm/alg/cc/conversation
Endpoints
| Method | Path | Handler | Request body | Source |
|---|---|---|---|---|
GET | /core2/tnt/dm/alg/cc/conversation/{convUuid}/message/{uuid} | get | — | MessageResourceController.java:160 |
DELETE | /core2/tnt/dm/alg/cc/conversation/{convUuid}/message/{uuid} | delete | — | MessageResourceController.java:196 |
GET | /core2/tnt/dm/alg/cc/conversation/{conversationUuid}/message/{messageUuid}/media | getMessageMedia | — | MessageResourceController.java:444 |
GET | /core2/tnt/dm/alg/cc/conversation/{conversationUuid}/messages/between-snapshot | getMessagesBetweenSnapshot | — | MessageResourceController.java:323 |
GET | /core2/tnt/dm/alg/cc/conversation/{conversationUuid}/messages/pagination | getListPagination | — | MessageResourceController.java:280 |
GET | /core2/tnt/dm/alg/cc/conversation/{conversation_uuid}/message/query | getList | — | MessageResourceController.java:233 |
POST | /core2/tnt/dm/alg/cc/conversation/{uuid}/message | create | MessageContainer | MessageResourceController.java:64 |
PUT | /core2/tnt/dm/alg/cc/conversation/{uuid}/message | update | MessageContainer | MessageResourceController.java:97 |
GET | /core2/tnt/dm/alg/cc/messages | getList | — | MessageResourceController.java:233 |
GET | /core2/tnt/dm/alg/cc/messages/between-snapshot | getMessagesBetweenSnapshot | — | MessageResourceController.java:323 |
GET | /core2/tnt/dm/alg/cc/messages/pagination | getListPagination | — | MessageResourceController.java:280 |
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