Skip to content
Endpoint–Predefined Message Links

Endpoint–Predefined Message Links

6 endpoints served by the EndpointPredefinedMessageLinkResourceController 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/endpoint-predefined-message-link
  • /core2/tnt/dm/alg/cc/endpoint-predefined-message-links

Endpoints

MethodPathHandlerRequest bodySource
POST/core2/tnt/dm/alg/cc/endpoint-predefined-message-linkcreateEndpointPredefinedMessageLinkContainerEndpointPredefinedMessageLinkResourceController.java:57
PUT/core2/tnt/dm/alg/cc/endpoint-predefined-message-linkupdateEndpointPredefinedMessageLinkContainerEndpointPredefinedMessageLinkResourceController.java:90
GET/core2/tnt/dm/alg/cc/endpoint-predefined-message-link/{uuid}get—EndpointPredefinedMessageLinkResourceController.java:153
DELETE/core2/tnt/dm/alg/cc/endpoint-predefined-message-link/{uuid}delete—EndpointPredefinedMessageLinkResourceController.java:184
GET/core2/tnt/dm/alg/cc/endpoint-predefined-message-linksgetList—EndpointPredefinedMessageLinkResourceController.java:216
GET/core2/tnt/dm/alg/cc/endpoint-predefined-message-links/paginationgetListPagination—EndpointPredefinedMessageLinkResourceController.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

Last updated on