Settings reference / Notifications
Notifications settings
Which events send a notification (email and/or ntfy), rate limits and alert thresholds. 22 settings on this tab.
Generated from the code. Defaults, ranges, choices, units and the live confirmation rule on this page are read from the settings schema each time the docs are generated, so they always match the bot.
Summary
All settings
Email: entry filled
email_on_fill
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Coin, side, entry, stop, leverage, margin, estimated liquidation.
What it does
Sends a notification when an entry order fills: coin, side, entry, stop, leverage, margin and estimated liquidation. It goes to every set-up channel (email and/or ntfy push).
Example
On: a fill sends something like [Wallbot PAPER] FILLED XRPUSDT long 20x @ 0.5123 with the stop and margin in the body.
When to change it
Turn it off if fills are frequent and you only care about closes and critical events.
Higher, lower, on or off
On: one notification per filled entry. Off: no fill notifications.
Risk notes
Low: notifications only. Each channel sends at most 30 per hour; extra ones are batched into one digest.
Email: position closed
email_on_close
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Coin, side, entry/exit, PnL (actual or estimated), fees, exit reason, duration.
What it does
Sends a notification when a position closes: coin, side, entry and exit, PnL (labelled actual or estimated), fees, exit reason, duration and trailing details. Sent to email and/or ntfy, whichever is set up.
Example
On: [Wallbot LIVE] CLOSED XRPUSDT long +12.4% (trailing stop), with PnL in USDT and fees in the body.
When to change it
Most traders keep it on. Turn it off if you review results only in the dashboard or the daily summary.
Higher, lower, on or off
On: one notification per closed trade. Off: no close notifications.
Risk notes
Low: notifications only.
Email: critical events
email_on_critical
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Stop placement failed, liquidation, daily loss limit, Binance 429/418 rate limits, entries paused by the bot, recording errors (at most one email per hour).
What it does
Sends a notification for critical events: stop placement failed, liquidation, loss cap reached, Binance 429/418 rate limits, entries paused, unprotected or lost positions, NOT SAFE TO STOP, key rejected, and recording errors (at most once per hour). Sent to email and/or ntfy.
Example
On: if a position has no confirmed stop on the exchange, you get [Wallbot LIVE] UNPROTECTED POSITION ... (repeated at most every 10 minutes per position).
When to change it
Keep it on whenever real money is involved. Turning it off means problems are only visible on the dashboard and in the log.
Higher, lower, on or off
On: critical events are notified. Off: no critical notifications, including loss-cap stops.
Risk notes
High if off in live: you may not learn about an unprotected position or a stopped bot until you look.
Email: server restarted
email_on_reboot
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: The VPS restarted unexpectedly and the @reboot entry started Wallbot (Trading: with entries paused). High priority on ntfy.
What it does
Sends an email / high-priority push when the server restarted on its own and the @reboot crontab entry started Wallbot again.
Example
On: at 03:12 Hostinger reboots the VPS; at about 03:14 your phone gets 'VPS rebooted — Wallbot started paused, check positions'.
When to change it
Leave it on: an unplanned restart is something you want to know about.
Higher, lower, on or off
On: you hear about the restart at once. Off: only the dashboard and the log show it.
Risk notes
Medium if off: positions may wait unchecked while entries stay paused.
Email: daily loss count reset
email_on_loss_reset
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Today's loss count for the live safety daily cap was reset (from the dashboard or on your request).
What it does
Sends an email / push when today's loss count for the live safety daily cap is reset, with the counted loss before and after.
Example
On: 'Daily loss count reset (by owner)': counted toward the daily cap -2.31 -> +0.00 USDT, caps unchanged.
When to change it
Leave it on: a reset changes how much the bot may lose today.
Higher, lower, on or off
On: every reset is notified. Off: only History and the Activity log show it.
Risk notes
Low.
Email: disk budget
email_on_disk
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Disk usage reaching the warning, high and pause levels of the disk budget, and recording paused or resumed.
What it does
Sends an email / push when disk usage reaches the warning, high or pause level of the disk budget, and when recording is paused or resumed.
Example
On: 'DISK 80% OF BUDGET' with the usage under /wallbot and the recordings' share.
When to change it
Leave it on on a shared server.
Higher, lower, on or off
On: you hear about disk problems. Off: only the dashboard and log show them.
Risk notes
Low. Off: a filling disk may go unnoticed.
Email: bot started
email_on_start
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Includes whether the previous stop was clean or abrupt.
What it does
Sends a notification when the engine starts, saying which books and execution exchange are used and whether the previous stop was clean or abrupt.
Example
On: after a crash and auto-restart, you get [Wallbot PAPER] STARTED paper on binance (previous stop: ABRUPT) a few seconds after a crash at 03:11, so you know it was a restart (1 email per start).
When to change it
Keep it on to notice unexpected restarts. Turn it off if you restart often on purpose.
Higher, lower, on or off
On: one notification per engine start. Off: none.
Risk notes
Low: notifications only. A start with entries paused is still sent as a critical event.
Email: settings changes
email_on_settings
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Every settings change (old -> new) and every mode switch.
What it does
Sends a notification for every settings change (old to new), every mode switch, and API key saves. The history entry is written either way.
Example
On: changing margin_pct from 10 to 8 sends "Settings changed on Trading ..." listing margin_pct: 10 -> 8.
When to change it
Keep it on for the live instance, so any change you did not make stands out. Turn it off while tuning many settings in paper.
Higher, lower, on or off
On: a notification per save or mode switch. Off: changes are only recorded in the history.
Risk notes
Low to medium: off means an unexpected change is not pushed to you.
Email: trade updates
email_on_trade_updates
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Re-anchoring to another wall after a pull, and take-profit changes (retargeted, removed).
What it does
Sends notifications while a trade is running: re-anchoring to another wall after a pull, absorbed-wall handling, stop tightened, moved to breakeven, holding in profit, trailing moves, re-plans and take-profit changes (set, retargeted, removed).
Example
On: a pulled wall with a backup sends RE-ANCHORED XRPUSDT long to wall 0.5080-0.5085; a trailing step sends TRAILING ... stop 0.5210 locks +50% ROE.
When to change it
Turn it off if these are too many and you only want fills, closes and critical events.
Higher, lower, on or off
On: running-trade updates are notified. Off: they appear only in the log and dashboard.
Risk notes
Low: notifications only. Many updates can hit the 30-per-hour cap and be batched into a digest.
Email: your manual positions
email_on_manual
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Alerts about positions you opened yourself (no stop, near liquidation, protecting wall pulled or broken, PnL milestones, closed with Binance's result) and Let Wallbot manage / Hand back. No-stop and near-liquidation alerts are high priority on ntfy.
What it does
Notifications about positions you opened yourself: no stop, near liquidation, protecting wall pulled or broken, PnL milestones, closed (Binance realized PnL, fees, funding), and Let Wallbot manage / Hand back. No-stop and near-liquidation are high priority on ntfy. Sent to email and/or ntfy.
Example
[Wallbot LIVE] MANUAL POSITION WITHOUT STOP BTCUSDT long 60 s after you open a long without a stop, repeated at most every 10 minutes.
When to change it
Keep on if you trade manually on the same account.
Higher, lower, on or off
On: these alerts are sent. Off: only the dashboard and the log show them.
Risk notes
Medium if off: you may miss a manual position near liquidation.
Email: volume target reached
email_on_volume
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Contract type volume: a quote's daily volume target was reached (once per quote per UTC day).
What it does
Contract type volume: a notification when a quote's daily volume target is reached (once per quote per UTC day).
Example
"VOLUME TARGET REACHED USDT 4012/4000".
When to change it
Keep on to know when entries switch quote.
Higher, lower, on or off
Off: the Activity log only.
Risk notes
None.
Email: recovery take profit on / off
email_on_recovery
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Recovery take profit became active or inactive (once per change).
What it does
A notification when the recovery take profit becomes active or inactive (once per change).
Example
"RECOVERY TP ON (today -0.42 USDT)".
When to change it
Keep on while trying the recovery take profit.
Higher, lower, on or off
Off: the Activity log only.
Risk notes
None.
Email: daily summary
email_on_daily
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Trades, wins/losses, total PnL, fees, cancelled entries, restarts, errors.
What it does
Sends a daily summary at email_daily_time: trades closed since local midnight, wins and losses, total PnL, fees, cancelled entries, restarts, critical events, recording errors and per-group totals.
Example
On with time 21:00: at 21:00 you get [Wallbot PAPER] DAILY 2026-10-01: 4 trades, +1.25 USDT.
When to change it
Keep it on for a once-a-day check. Turn it off if you prefer the dashboard.
Higher, lower, on or off
On: one summary per local day. Off: no summary.
Risk notes
Low: notifications only.
Daily summary time
email_daily_time
- Default
- 21:00
- Range
- Free text
- Type
- text
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Local time of the server, HH:MM (24 h).
What it does
When the daily summary is sent, in the server PC's local time, written HH:MM (24 h). It is sent once per local day, the first time the bot runs at or after this time.
Example
Time 21:00: the summary goes out at 21:00. If the bot was off then and starts at 22:15 the same day, it sends that day's summary right away. Typing 7:30 is saved as 07:30.
When to change it
Pick a time you usually check messages. It only matters when email_on_daily is on.
Higher, lower, on or off
Earlier: the summary covers a shorter part of the day (it always counts from local midnight). Later: it covers more of the day.
Risk notes
Low: notifications only.
Notifications per hour
notify_max_per_hour
- Default
- 30
- Range
- 1 to 1000
- Type
- Whole number
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Cap per channel (email, push); critical alerts count too.
What it does
Caps how many notifications each channel (email and ntfy push, each counted separately) sends in any rolling hour. Critical alerts count toward the cap. Messages beyond the cap are collected and sent as one digest as soon as the cap allows.
Example
Cap 30: during a busy hour 45 emails are due. The first 30 go out one by one; the other 15 are bundled into a digest that is sent when the oldest email drops out of the rolling hour.
When to change it
Raise it if you need every alert promptly. Lower it to avoid flooding your inbox or phone, or to stay within your email provider's limits.
Higher, lower, on or off
Higher: more individual messages, faster delivery in busy periods. Lower: fewer messages, more alerts arrive late inside a digest.
Risk notes
Medium if set very low: an urgent alert can be delayed into a digest. Never affects trading.
Unconfirmed cancel alert after
cancel_alert_after_s
- Default
- 60 s
- Range
- 5 to 3600 s
- Type
- Number
- Unit
- s
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: A high-priority notification when an entry cancel is still unconfirmed after this long.
What it does
While an entry cancel is being retried (cancel_retry_until_confirmed), a critical log line and a high-priority notification are sent once, when the cancel is still unconfirmed after this long. The bot keeps retrying after the alert.
Example
60 s: a cancel fails at 10:00:00. Retries continue; at about 10:01:00 it is still not confirmed, so you get "ENTRY CANCEL NOT CONFIRMED" telling you to check the exchange's open orders.
When to change it
Lower it if you want to hear about stuck cancels sooner. Raise it if short exchange hiccups wake you up too often.
Higher, lower, on or off
Higher: fewer alerts, later warning of a real problem. Lower: earlier alerts, more of them for problems that would have cleared by themselves.
Risk notes
Low to medium. A high value delays your warning about an order that may still be resting.
Critical alerts are high priority on ntfy
ntfy_critical_high_priority
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Every notification of the 'critical' type (e.g. STARTED PAUSED, NOT SAFE TO STOP, key rejected, entry cancel not confirmed, loss cap reached) is pushed to ntfy at high priority (4). Off: only titles with CRITICAL, LIQUIDATED, RATE LIMIT, RECORDING ERRORS, BOT EXITED or STOP FAILED are high priority. Email is unaffected.
What it does
Pushes every critical-type notification to ntfy at high priority (4), so your phone treats it as urgent. Critical types include STARTED PAUSED, NOT SAFE TO STOP, BINANCE KEY REJECTED, ENTRY CANCEL NOT CONFIRMED, TRADING STOPPED (loss cap), LOST ORDER, UNPROTECTED POSITION and liquidations. Email is not affected; it has no priority.
Example
After a restart the Trading instance starts paused and sends [Wallbot LIVE] STARTED PAUSED. On: it arrives at priority 4. Off: priority 3, because the title has none of the 6 high-priority words (CRITICAL, LIQUIDATED, RATE LIMIT, RECORDING ERRORS, BOT EXITED, STOP FAILED).
When to change it
Leave it on if ntfy is your alarm for things that need you. Turn it off if high-priority pushes for lower-stakes critical events (for example BINANCE KEY OK AGAIN, which is also critical-type) are too noisy.
Higher, lower, on or off
On: all critical-type pushes are high priority, plus any title with one of the 6 keywords. Off: only titles with one of the 6 keywords are high priority; the rest arrive at normal priority.
Risk notes
Low. Only the push priority changes, never which notifications are sent. Off makes it easier to miss STARTED PAUSED or NOT SAFE TO STOP.
Alert when the live key is rejected
key_rejected_alert
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Binance rejecting the live key (-2015: invalid key, IP or permissions) shows a dashboard banner while it happens and sends a high-priority notification with the request IP Binance reports; a new IP is reported at once so it can be added to the key's allow-list.
What it does
When Binance rejects the live API key (-2015: invalid key, IP or permissions), the dashboard shows a banner while it lasts and Wallbot sends a high-priority notification with the request IP Binance reports. An IP never seen in a rejection before is reported at once, so you can add it to the key's allow-list.
Example
Your router gets a new public IP. Binance starts answering -2015 with "request ip: 203.0.113.7". The banner appears straight away, and because 203.0.113.7 is new, an alert is sent at once. The banner clears after 2 minutes without a rejection.
When to change it
Leave it on for live. Only the live account is checked, not testnet or paper.
Higher, lower, on or off
On: banner and alerts as described, tuned by key_rejected_threshold and key_rejected_alert_min. Off: rejections are only visible as failing orders and errors in the log.
Risk notes
Medium if off: while the key is rejected, orders, cancels and position checks fail at random, and you may not notice.
Key rejections before alerting
key_rejected_threshold
- Default
- 3
- Range
- 1 to 100
- Type
- Whole number
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: Alert after this many -2015 rejections within 60 s.
What it does
How many -2015 key rejections within 60 seconds are needed before the repeating alert is sent. A new IP is always reported at once, whatever this number.
Example
At 3: two rejections in a minute show the banner but send no alert (unless the IP is new). The third rejection within 60 seconds sends the alert.
When to change it
Raise it if single, harmless rejections cause alerts. Lower it to 1 if you want to hear about every rejection.
Higher, lower, on or off
Higher: fewer alerts, short bursts are ignored. Lower: alerts on the first sign of trouble.
Risk notes
Low: only changes when you are notified; the banner shows every rejection.
Key rejection alert interval
key_rejected_alert_min
- Default
- 15 min
- Range
- 1 to 1440 min
- Type
- Number
- Unit
- min
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: At most one key-rejection alert per this many minutes (a new IP is always reported).
What it does
The minimum gap between two repeating key-rejection alerts. A rejection from a new IP is always reported immediately.
Example
At 15 minutes: the key is rejected continuously from 10:00 to 10:40. You get alerts at about 10:00, 10:15 and 10:30, not one per rejection.
When to change it
Raise it if a long outage floods your inbox; lower it if you want more frequent reminders.
Higher, lower, on or off
Higher: fewer repeated alerts. Lower: more frequent reminders while the problem lasts.
Risk notes
Low: notification frequency only.
Email: delisting announced
email_on_delist
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: A Binance delisting / contract-removal announcement for a coin Wallbot knows (high priority), with your open Wallbot and manual positions on that coin.
What it does
Sends a high-priority email / push when a Binance delisting or contract-removal announcement affects a coin Wallbot knows: the announcement, the affected contracts, cancelled pending entries and your open Wallbot and manual positions on that coin. The listening instance always sends it; the other instance only when it holds positions on that coin.
Example
'DELISTING XYZ: new entries blocked - POSITIONS OPEN' with 'Your manual positions on these coins: long XYZUSDT qty 120 entry 0.4512'.
When to change it
Leave it on.
Higher, lower, on or off
On: you hear about delistings at once. Off: only the log and the Events panel show them.
Risk notes
Medium when off: a delisting could go unnoticed for a manual position.
Email: unlock-short paper test
email_on_unlock_short
- Default
- On
- Range
- On or off
- Type
- On/off
- Live confirmation
- No. Changes apply in every mode without the typed confirmation.
In the dashboard: The unlock-short test's daily opens/closes, settlements and stop-variant notices; data-check failures and HOLD are high priority.
What it does
Notifications of the unlock-short paper test: each 00:00 UTC roll that opens, closes or skips pairs, each settled pair's results, the stop variant triggering, and (high priority) a failed data check or HOLD.
Example
'UNLOCK-SHORT 2 opened, 1 closed' at 00:00 UTC; 'UNLOCK-SHORT DATA CHECK FAILED' if DefiLlama's files are more than 36 h old.
When to change it
Leave it on while the test runs.
Higher, lower, on or off
On: you see the test day by day. Off: only the dashboard panel shows it.
Risk notes
Low.