Telegram Messages
7 endpoints served by the TelegramMessageController 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 |
|---|---|---|---|---|
POST | /core2/tnt/dm/alg/cc/telegram-api/send | sendMessage | MessageContainer | TelegramMessageController.java:147 |
POST | /core2/tnt/dm/alg/cc/telegram-api/send-external | sendExternalMessage | Map<String,Object> | TelegramMessageController.java:313 |
POST | /core2/tnt/dm/alg/cc/telegram-api/send/broadcast | broadcastMessage | Map<String, Object> | TelegramMessageController.java:231 |
POST | /core2/tnt/dm/alg/cc/telegram-api/send/media | sendTelegramMedia | — | TelegramMessageController.java:190 |
POST | /core2/tnt/dm/alg/cc/telegram-api/{tenantCode}/{botId}/receive | receiveMessage | — | TelegramMessageController.java:87 |
GET | /core2/tnt/dm/alg/cc/telegram-api/{tenantCode}/{telegramId}/set-webhook | setWebhookUrl | — | TelegramMessageController.java:54 |
GET | /core2/tnt/dm/alg/cc/telegram-api/{tenantCode}/{telegramId}/webhook-info | getWebhookInfo | — | TelegramMessageController.java:62 |
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