Email Thread Events
6 endpoints served by the EmailThreadEventResourceController 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/email-thread-event/core2/tnt/dm/alg/cc/email-thread-events
Endpoints
| Method | Path | Handler | Request body | Source |
|---|---|---|---|---|
POST | /core2/tnt/dm/alg/cc/email-thread-event | create | EmailThreadEventContainer | EmailThreadEventResourceController.java:56 |
PUT | /core2/tnt/dm/alg/cc/email-thread-event | update | EmailThreadEventContainer | EmailThreadEventResourceController.java:90 |
GET | /core2/tnt/dm/alg/cc/email-thread-event/{uuid} | get | — | EmailThreadEventResourceController.java:153 |
DELETE | /core2/tnt/dm/alg/cc/email-thread-event/{uuid} | delete | — | EmailThreadEventResourceController.java:186 |
GET | /core2/tnt/dm/alg/cc/email-thread-events | getList | — | EmailThreadEventResourceController.java:219 |
GET | /core2/tnt/dm/alg/cc/email-thread-events/pagination | getListPagination | — | EmailThreadEventResourceController.java:258 |
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