Proposal: Optional third-party HTTP API for TradeBot (WebUI and similar clients)

[metalisk]

Context

We are designing an optional Bot API v1 so external clients (starting with a graphical WebUI) can monitor and control a trade bot without going through ADAMANT Messenger or Telegram.

The WebUI never talks to exchanges directly. It only talks to the bot API. The bot remains the single source of market data (ticker, order book, trades, OHLC), account state, trade parameters, and command execution.

Goals

• Optional inbound HTTP + WebSocket API on the bot (private_webui port in config)
• JWT auth verified on the bot (private_webui_secret_key); user accounts live in the external client
• Structured JSON endpoints for market/account/params plus command wrappers
• GET /bot bootstrap with capabilities (installed mm_*.js modules and exchange feature flags)
• WebSocket params:updated for live trade-parameter changes
• Transport modes: directHttp (self-hosted clients) and later relayWs (subscription hosting)

Non-goals (this thread)

• Payment, billing, or license UI (separate product)
• WebUI implementation details (see companion discussion for WebUI)

Request for feedback

1. Should this API live in the open-source adamant-tradebot repo as an optional module?
2. Which endpoints are required for a minimal useful client beyond messenger commands?
3. Polling vs push for market/account data on v1?

A tracking issue will be opened in adamant-tradebot referencing this discussion.

Related: premium reference implementation is in progress on adamant-tradebot-me branch refactor/new-webui-api.

[adamantmm]

Great and in time.
Issue created: [Feat] Optional Bot API v1 for third-party clients (WebUI and similar) Adamant-im/adamant-tradebot#104