Preferred Agent Assignments
4 endpoints served by the PreferredAgentAssignmentController 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.
Access endpoints present: backoffice-ep, etl-ep, login-entity-ep. The segment decides how the caller authenticates — see Authentication and the Data API reference for the credential each one takes, the request headers, and the response envelope. Paths without an access segment take the signed-in user’s token.
Endpoints
| Method | Path | Handler | Request body | Source |
|---|---|---|---|---|
POST | /core2/tnt/dm/alg/cc/preferred-agent-assignment | assignPreferredAgent | ConversationRequest | PreferredAgentAssignmentController.java:69 |
POST | /core2/tnt/dm/alg/cc/preferred-agent-assignment/backoffice-ep | assignPreferredAgentBackOfficeEP | ConversationRequest | PreferredAgentAssignmentController.java:101 |
POST | /core2/tnt/dm/alg/cc/preferred-agent-assignment/etl-ep | assignPreferredAgentEtlEP | ConversationRequest | PreferredAgentAssignmentController.java:128 |
POST | /core2/tnt/dm/alg/cc/preferred-agent-assignment/login-entity-ep | assignPreferredAgentLoginEntityEP | ConversationRequest | PreferredAgentAssignmentController.java:155 |
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