Endpoint Headers
4 endpoints served by the EndpointHdrController 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.
Endpoints
| Method | Path | Handler | Request body | Source |
|---|---|---|---|---|
PUT | /core2/tnt/dm/alg/cc/endpoints | updateEndpoint | EndpointHdrContainer | EndpointHdrController.java:124 |
GET | /core2/tnt/dm/alg/cc/endpoints/id/{endpointId} | getEndpointById | — | EndpointHdrController.java:80 |
GET | /core2/tnt/dm/alg/cc/endpoints/query | getByCriteria | — | EndpointHdrController.java:56 |
GET | /core2/tnt/dm/alg/cc/endpoints/{guid} | getEndpointByGuid | — | EndpointHdrController.java:102 |
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