Skip to content
Unified Contact Center API

Unified Contact Center API

The Unified Contact Center (UCC) is the omnichannel messaging half of BigLedger — agents, conversations, channels, messages, canned replies, and the connectors that carry WhatsApp Business, Telegram, Lazada and email traffic in and out. Its HTTP surface is served under /core2/tnt/dm/alg/cc/… (one WhatsApp controller sits under /core2/tnt/dm/ucc/…).

What is here, and what is not. The backend serves 965 routes across 82 controllers in this family. The 35 pages below document 357 of them, one page per controller, and every path on every page is a row in the generated route table named in the front matter — nothing here is typed by hand. The other 47 controllers (task queues, squads, template messages, quality control, virtual contacts, rules, reports, the bot surface) are in data/routes.tsv and will be rendered from it the same way; until then, ask your BigLedger contact for the route rather than guessing at it.

Each page lists, per endpoint, the HTTP method, the path with variables as {name}, the handler, the declared request-body type, and the controller file and line. Behaviour is not described, because it has not been read — what the pages promise is that the path exists at the named commit. Most controllers expose the same six-method shape three times over, once per access endpoint (backoffice-ep for a signed-in back-office user, etl-ep for an access key, login-entity-ep for a customer or supplier login); Authentication explains the credential each one takes and the Data API reference the headers, paging and envelope.

Controllers with a page

Related

Last updated on