Skip to content

Predefined Message Lines

6 endpoints served by the PredefinedMessageLineResourceController 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/predefined-message-line
  • /core2/tnt/dm/alg/cc/predefined-message-lines

Endpoints

MethodPathHandlerRequest bodySource
POST/core2/tnt/dm/alg/cc/predefined-message-linecreatePredefinedMessageLineContainerPredefinedMessageLineResourceController.java:57
PUT/core2/tnt/dm/alg/cc/predefined-message-lineupdatePredefinedMessageLineContainerPredefinedMessageLineResourceController.java:89
GET/core2/tnt/dm/alg/cc/predefined-message-line/{uuid}get—PredefinedMessageLineResourceController.java:152
DELETE/core2/tnt/dm/alg/cc/predefined-message-line/{uuid}delete—PredefinedMessageLineResourceController.java:183
GET/core2/tnt/dm/alg/cc/predefined-message-linesgetList—PredefinedMessageLineResourceController.java:215
GET/core2/tnt/dm/alg/cc/predefined-message-lines/paginationgetListPagination—PredefinedMessageLineResourceController.java:253

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