Proposal: Optional third-party HTTP API for TradeBot (WebUI and similar clients) #48
metalisk
started this conversation in
MarketMaking.app
Replies: 1 comment
-
|
Great and in time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
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
private_webuiport in config)private_webui_secret_key); user accounts live in the external clientGET /botbootstrap with capabilities (installedmm_*.jsmodules and exchange feature flags)params:updatedfor live trade-parameter changesdirectHttp(self-hosted clients) and laterrelayWs(subscription hosting)Non-goals (this thread)
Request for feedback
adamant-tradebotrepo as an optional module?A tracking issue will be opened in
adamant-tradebotreferencing this discussion.Related: premium reference implementation is in progress on
adamant-tradebot-mebranchrefactor/new-webui-api.Beta Was this translation helpful? Give feedback.
All reactions