Bot Service

Bot Service connects messaging workflows to OpenEdge. It supports Telegram-style bot webhooks, chat/message views, widget chat routes, interactions, file forwarding, and reply flows.

Core Routes

/v1/apps/bot
/v1/apps/bot/webhook
/v1/apps/bot/widget
/v1/apps/bot/ws

The console also exposes Bot Service configuration and webhook status checks.

Service Configuration

Create a bot instance from the console:

{
  "service_id": "bot",
  "alias": "alerts",
  "config": {
    "platform": "telegram",
    "webhook_url": "https://example.com/internal/bot-events",
    "bot_token": "123456:ABC..."
  },
  "status": "active"
}

When a Telegram bot token is configured, OpenEdge can bind the Telegram webhook to the gateway route and forward incoming updates to your business endpoint.

Common Capabilities

Capability	Route family
Chat list and message history	/v1/apps/bot/chats
Interactions	/v1/apps/bot/interactions
Send reply	/v1/apps/bot/messages/reply
Send file	/v1/apps/bot/messages/send-file
Widget token and chat	/v1/apps/bot/widget/*

Authentication

Most Bot API routes require an authenticated user or API key. Use least-privilege scopes for production keys.

Recommended scopes:

bot:send
bot:read

Operational Notes

• Store bot tokens as service configuration only through the console.
• Do not log raw Telegram payloads if they contain private user data.
• Use webhook status checks in the console to verify that Telegram is bound to the expected gateway URL.