Alerts

Alerts watch a condition and tell you when it becomes true. The simplest kind is a price level. Beyond that you can alert on an indicator value, on a crossing between any two plotted series, on a drawing being touched, on a screener membership change, or on an alert.when condition declared inside a script — which is the most precise option, because the condition is expressed in the same code that draws the signal.

Every alert has a trigger mode. Once fires a single time and disarms itself. Once per bar fires at most once inside each interval. Once per bar close waits for the bar to finish before evaluating, which is the mode you want for anything you intend to trade, because a provisional bar can cross a level and then close back below it.

Delivery goes to the in-app inbox, to email, to push notification on mobile, or to a webhook. The webhook payload is JSON and includes the symbol, timeframe, condition name, price at fire time, the ISO timestamp and any message template you wrote in the script. Message templates interpolate placeholders such as symbol, close and the value of any named plot.

Webhooks are signed with an HMAC over the raw request body, sent in the x-algobeam-signature header. Verify it before acting on the payload — the endpoint is public, and an unverified webhook receiver that places orders is a liability. The verifyAlertSignature helper in AlgoBeamTS does the comparison in constant time.

Rate control keeps a noisy script from flooding you. Each alert has a cooldown, a daily cap and an optional quiet window, and repeated fires inside the cooldown are counted and collapsed into one notification rather than dropped silently.