Login Subject Links
6 endpoints served by the LoginSubjectLinkController 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 |
|---|---|---|---|---|
GET | /core2/tnt/dm/alg/cc/login-subject-link | getAllLoginSubjectLink | — | LoginSubjectLinkController.java:132 |
POST | /core2/tnt/dm/alg/cc/login-subject-link | createLoginSubjectLink | LoginSubjectLinkContainer | LoginSubjectLinkController.java:53 |
PUT | /core2/tnt/dm/alg/cc/login-subject-link | updateLoginSubjectLink | LoginSubjectLinkContainer | LoginSubjectLinkController.java:78 |
GET | /core2/tnt/dm/alg/cc/login-subject-link/query | getLoginSubjectLinkByCriteria | — | LoginSubjectLinkController.java:182 |
GET | /core2/tnt/dm/alg/cc/login-subject-link/{guid} | getLoginSubjectLinkByGuid | — | LoginSubjectLinkController.java:154 |
DELETE | /core2/tnt/dm/alg/cc/login-subject-link/{guid} | deleteLoginSubjectLink | — | LoginSubjectLinkController.java:105 |
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