Auto-generated. This article is rebuilt from FastAPI route introspection by scripts/build_api_kb.py. Edit the route docstring in app/ and re-run the script — do not edit this file directly.

GET /api/v1/alerts/active

Handler: app.signals.routes.get_active_alerts
Methods: GET

Description

Currently-firing market-signal alerts, sorted by severity then newest first.

Two DEFAULT filters make this feed answer “what is the market doing now?” rather than “what has ever fired and not been cleaned up”. Both are read-side only — no alert row is mutated, and both are echoed on the response so nothing is filtered silently.

Recency (window_hours, default 168 = 7d). An alert whose condition still holds has its fired_at refreshed on every capture cycle, so a genuinely-current alert is minutes old in market hours and at most a closed-weekend gap old otherwise. Rows far outside that window are fossils: a cross-detection alert (a transition event — GEX_FLIP_NEG, ZGL_BREACH_DOWN, REGIME_CHANGE, …) is never resolved when its condition stops holding, so it keeps state='active' with the message and price it was rendered with weeks ago. Pass a larger window_hours (up to 8760) to read them anyway.

Ops split (include_ops, default false). Platform-internal alerts — frozen-feed / stale-input data-integrity guards and the AI-pipeline health guards — describe the platform, not the market. They are excluded by default so a consumer reading market state is not handed pipeline noise, and included with include_ops=true. Every alert object carries an ops boolean either way.

An alert whose fired_at cannot be parsed is KEPT (fail open) rather than silently dropped.

Counts reconcile exactly: len(alerts) + filtered.stale + filtered.ops == total_active. The two filtered counters are disjoint — an ops alert that is also stale is counted once, under ops.

Parameters

Curl

curl -s https://bigclawd.com/api/v1/alerts/active