Telegram bot
The Telegram integration uses a webhook-based architecture. Hyperoru receives messages from Telegram’s API and responds through the bot.Setup
Create a Telegram bot
Message @BotFather on Telegram:
- Send
/newbot - Choose a name and username
- Copy the bot token
Set the webhook with Telegram
Hyperoru automatically registers the webhook with Telegram’s API. Verify it’s active:
Discord bot
The Discord integration uses a gateway-based connection, maintaining a persistent WebSocket to Discord’s API.Setup
Create a Discord application
- Go to the Discord Developer Portal
- Create a new application
- Navigate to the Bot section and create a bot
- Copy the bot token
- Enable the Message Content Intent under Privileged Gateway Intents
Invite the bot to your server
Generate an invite URL with these permissions:
- Send Messages
- Read Message History
- Embed Links
Notification types
Both Telegram and Discord support the same notification categories:| Notification | Trigger | Content |
|---|---|---|
| Trade Executed | Order filled on exchange | Symbol, direction, size, entry price |
| Position Closed | Position closed (TP/SL/manual) | Symbol, PnL, duration, exit reason |
| Signal Fired | Signal pool conditions met | Pool name, triggered signals, matched values |
| Strategy Error | Strategy execution failed | Error type, trader name, details |
| Daily Summary | Scheduled (configurable time) | PnL, open positions, active traders |
Notification preferences
Configure which notifications you receive:Chat bindings
Bind a bot to a specific trader to scope notifications and commands:- Send notifications for a specific trader to a dedicated channel
- Use chat commands to query that trader’s status, positions, and history
- Route different traders to different channels for organized monitoring
Multiple bindings
Bind multiple traders to different channels for organized notification routing.
Chat commands
Query positions, PnL, and trader status directly from Telegram or Discord.
Bot tokens are stored encrypted in the database using the same encryption key as exchange credentials. Keep your
HYPERLIQUID_ENCRYPTION_KEY secure.