Skip to content

Emails

9 endpoints served by the EmailResourceController 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/emails
  • /core2/tnt/dm/alg/cc/email-thread

Endpoints

MethodPathHandlerRequest bodySource
GET/core2/tnt/dm/alg/cc/email-thread/{emailThreadUuid}/email/{emailUuid}/attachment/{attachmentIndex}getEmailAttachment—EmailResourceController.java:352
GET/core2/tnt/dm/alg/cc/email-thread/{emailThreadUuid}/emailsgetList—EmailResourceController.java:233
GET/core2/tnt/dm/alg/cc/email-thread/{emailThreadUuid}/emails/paginationgetListPagination—EmailResourceController.java:281
GET/core2/tnt/dm/alg/cc/email-thread/{threadUuid}/email/{uuid}get—EmailResourceController.java:170
DELETE/core2/tnt/dm/alg/cc/email-thread/{threadUuid}/email/{uuid}delete—EmailResourceController.java:201
POST/core2/tnt/dm/alg/cc/email-thread/{uuid}/emailcreateEmailContainerEmailResourceController.java:74
PUT/core2/tnt/dm/alg/cc/email-thread/{uuid}/emailupdateEmailContainerEmailResourceController.java:107
GET/core2/tnt/dm/alg/cc/emailsgetList—EmailResourceController.java:233
GET/core2/tnt/dm/alg/cc/emails/paginationgetListPagination—EmailResourceController.java:281

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