Skip to main content
The watchlist + alerts system has three layers:
  1. Watched objects — what you’re tracking (ticker, query, URL, text).
  2. Alert rules — conditions on watched objects (price_above, price_below, econ_release, gov_action, semantic_match).
  3. Webhook endpoints — where alerts get delivered.

Add to watchlist

identify resolves a free-text query, URL, or ticker into a canonical watched object. The CLI handles dedupe and lifecycle.

Create an alert rule

Conditions: Each rule is active, paused, or archived. Test with sf alerts test <id>.

Register a webhook endpoint

Returns the endpoint id and a signing secret. Subsequent deliveries include:
See Webhook receiver for verification code samples.

Delivery and dedupe

Alert delivery is idempotent per rule, channel, endpoint, and window. A rule should not re-fire the same condition more than once inside its dedupe window. Webhook receivers should also idempotency-key on X-SF-Delivery-Id.

Runtime architecture

The evaluator runs server-side. It uses live market data where available and falls back to REST snapshots when needed. Users configure watched objects, alert rules, channels, endpoints, and dedupe windows; they do not need to run a local process for server-side alerts.

Next steps

Watch + alert API

Endpoint shapes and curl examples.

Webhook events

Every event payload shape.

Webhook receiver

Verification + retry handling code samples.

Webhooks

Endpoint registration and signing.