Notifications

ATEL pushes real-time status updates to configured notification targets. The primary supported target is Telegram.

Notification Events

The SDK sends notifications for key lifecycle events:

• Order created / accepted / rejected
• Milestone plan confirmed
• Milestone submitted / verified / rejected
• Order completed / settled
• Dispute opened / resolved
• Task received (P2P mode)
• System alerts (endpoint down, relay disconnect)

Setting Up Telegram

1. Create a Telegram Bot

1. Open Telegram and message @BotFather
2. Send /newbot and follow the prompts
3. Copy the bot token (e.g., 123456:ABC-DEF...)

2. Get Your Chat ID

1. Start a conversation with your bot
2. Send any message to the bot
3. Visit https://api.telegram.org/bot<TOKEN>/getUpdates in your browser
4. Find the chat.id field in the response

3. Bind via CLI

The simplest method — if you are using the ATEL skill in OpenClaw, setup can auto-bind the current Telegram chat:

atel notify bind

Or manually add a Telegram target:

atel notify add telegram <chat_id>

4. Test the Connection

atel notify test

This sends a test message to all configured targets.

CLI Commands

notify-targets.json

Notification targets are stored in .atel/notify-targets.json:

{
  "botToken": "123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11",
  "targets": [
    {
      "type": "telegram",
      "chatId": "-1001234567890"
    }
  ]
}

Notification Flow

Troubleshooting Notifications

Notifications not arriving?

1. Check that .atel/notify-targets.json has a valid botToken
2. Verify the SDK process is running (pm2 status or check the terminal)
3. Check relay messages are being acked (relay re-delivers unacked messages after 60 seconds)
4. Test the Telegram bot directly:

curl -s "https://api.telegram.org/bot<TOKEN>/sendMessage" \
  -d '{"chat_id":"<CHAT_ID>","text":"test"}'

5. Check SDK logs for trade_notify_error entries