Skip to content

Commit

Permalink
fix(docs): format JSON example for Telegram bot configuration
Browse files Browse the repository at this point in the history
  • Loading branch information
fassko committed Jan 9, 2025
1 parent be0511e commit 55a52da
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions docs/fassets/guides/7-telegram-bot-notifications.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -11,13 +11,13 @@ keywords: [fassets, xrp, btc, doge flare-network, flare-network]
1. Get the API key from the [FAssets Telegram Bot](http://t.me/FlareFAssetsSongbirdBot) by sending `/events` and selecting `Subscribe to Events`.
2. Add the following configuration to the `apiNotifierConfigs` list in the `config.json` file, replacing `API_KEY` with the key obtained from the bot.

```json
{
"apiKey": "API_KEY",
"apiUrl": "https://fasset-tg-bot-songbird.flare.network",
"level": "danger"
}
```
```json
{
"apiKey": "API_KEY",
"apiUrl": "https://fasset-tg-bot-songbird.flare.network",
"level": "danger"
}
```

:::info
Please note that notifications will only be sent out for **danger** and **critical** levels, regardless of the configured level. This is enforced by the Telegram bot, which ignores other events to prevent unnecessary HTTP requests.
Expand Down

0 comments on commit 55a52da

Please sign in to comment.