Lazada Messages
5 endpoints served by the LazadaMessageController 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/lazada-api/auth | auth | — | LazadaMessageController.java:55 |
GET | /core2/tnt/dm/alg/cc/lazada-api/auth/callback | redirectUri | — | LazadaMessageController.java:67 |
POST | /core2/tnt/dm/alg/cc/lazada-api/send | sendMessage | MessageContainer | LazadaMessageController.java:110 |
POST | /core2/tnt/dm/alg/cc/lazada-api/send/media | sendLazadaMedia | — | LazadaMessageController.java:138 |
POST | /core2/tnt/dm/alg/cc/lazada-api/{tenantCode}/receive | receive | — | LazadaMessageController.java:96 |
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