---
title: "Api V2 Signals Signal Name Events Get"
method: GET
path: "/api/v2/signals/{signal_name}/events"
tags: ["Trade Signals (v2)"]
---

# Api V2 Signals Signal Name Events Get

`GET /api/v2/signals/{signal_name}/events`

## Request

- Base URL: `https://api.zerogex.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.zerogex.io/api/v2/signals/{signal_name}/events`
- Auth: HTTP bearer

Time-stamped history of a single signal's scores with direction-flip detection and realized returns.

Provides per-bar snapshots of a component's score, direction, and input context,
plus *forward* realized returns for backtesting and diagnostic overlays.

The returned window always spans the two most-recent regular trading
sessions: the current session plus the previous one when the market is
live, or the two most-recent fully-elapsed sessions otherwise. ``limit``
acts as a safety cap on result size for unusually dense signals.

**Params:**
- `signal_name` — one of: `vol_expansion`, `eod_pressure`, `squeeze_setup`,
  `trap_detection`, `zero_dte_position_imbalance`, `gamma_vwap_confluence`,
  `range_break_imminence`, `market_pressure`, `positioning_trap`,
  `vanna_charm_flow`.  Returns 400 for unknown names.
- `symbol` (default `SPY`).
- `limit` — 1–1000, default 1000 (cap on row count within the session window).
- `horizon` — `"30m"` | `"60m"` | `"120m"` (default `"60m"`); forward window for realized return.

**Returns:**
```json
{
  "underlying": "SPY",
  "signal_name": "vol_expansion",
  "horizon": "60m",
  "rows": [
    {
      "underlying": "SPY",
      "timestamp": "2026-04-22T14:55:00Z",
      "component_name": "vol_expansion",
      "score": 42.31,
      "weighted_score": 0.0846,
      "weight": 0.20,
      "direction": "bullish",
      "direction_flip": true,
      "inputs": { "...context_values snapshot..." },
      "close": 677.12,
      "horizon_close": 678.40,
      "realized_return": 0.00189
    }
  ],
  "count": 100,
  "summary": {
    "flips": 7,
    "bullish": 43, "bearish": 38, "neutral": 19,
    "latest_timestamp": "...",
    "latest_direction": "bullish"
  }
}
```

- `score` — clamped_score × 100; [-100, +100].
- `direction_flip` — `true` when sign changed since previous non-zero row.
- `realized_return` — (horizon_close − close) / close; 6-decimal fractional;
  `null` if no forward quote exists yet.
- `horizon_close` — underlying close at `timestamp + horizon`.

**Trader interpretation:**
- Use `realized_return` to validate direction (bullish rows should average positive returns).
- Low `flips` count = cleaner trend-following signal.
- `direction_flip` markers make great overlay pins on a price chart.

**Page design.** Time-series panel: top line = `score` colored by direction;
bottom histogram of `realized_return`. Triangle glyphs at each `direction_flip`.
KPI row from `summary`.

## Path parameters

- `signal_name` string, required

## Query parameters

- `symbol` string
- `limit` integer
- `horizon` string

## Response `200`

Successful Response

- EnvelopeAny
  - `data` unknown, required
  - `freshness` Freshness, required: The v2 freshness envelope. Present on every ``/api/v2/*`` response.
    - `evaluated_at` string, date-time, required: When the API evaluated this response (server wall clock, UTC). Endpoint-health signal: advances on every request even when the underlying data is unchanged.
    - `generated_at` string, date-time, required: When the served data was computed. Equals the snapshot stamp for cycle-backed endpoints, or evaluated_at for endpoints computed on demand for this request.
    - `source_timestamp` string, date-time, nullable: Timestamp of the upstream market observation the payload derives from. This is what freshness_status is measured against. Null when the endpoint has no upstream feed or returned no rows.
    - `latest_event_at` string, date-time, nullable: Newest event timestamp present in the payload (last bar, last trade, last scored row). Best-effort on very large responses, which are sampled rather than fully walked.
    - `age_seconds` number, nullable: evaluated_at - source_timestamp, in seconds. Null when source_timestamp is null.
    - `market_session_status` string, required: pre-market | regular | after-hours | closed (US/Eastern).
    - `expected_update_cadence` string, nullable: ISO-8601 duration for how often this endpoint's data is expected to change right now, e.g. PT60S. Null means no updates are expected (weekend, holiday, or a feed that only runs during the session).
    - `expected_update_cadence_seconds` number, nullable: expected_update_cadence as a number of seconds.
    - `cadence_profile` string, required: Identifier of the cadence class this endpoint belongs to, e.g. analytics_cycle. Stable across releases; the seconds behind it may be retuned.
    - `stale_after` string, date-time, nullable: Instant after which this payload should be treated as stale. Null whenever expected_update_cadence is null.
    - `freshness_status` 'fresh' | 'aging' | 'stale' | 'session_closed' | 'static' | 'unknown', required: The rolled-up freshness verdict for one response. ``fresh`` ``source_timestamp`` is within one expected update cadence. ``aging`` Past one cadence but not yet past ``stale_after`` — the grace band that absorbs normal cycle jitter. Not an error; a client that polls faster than the cadence sees this routinely. ``stale`` Past ``stale_after`` while updates *were* expected. This is the actionable state: the feed behind this endpoint is late. ``session_closed`` A feed-backed endpoint whose feed is not due to produce anything right now (weekend, holiday, or a feed that only runs during the session). The payload is the last good value — deliberately NOT reported as ``stale``, because an overnight consumer polling a closed market is not observing a fault and should not page on it. ``static`` The endpoint is not feed-backed at all: completed history, or a result computed from the caller's own inputs. Age here carries no health meaning and never becomes a fault. ``unknown`` No source timestamp could be resolved from the payload (e.g. a pure calculator, an admin endpoint, or an empty result set). A consumer should fall back to ``evaluated_at`` for endpoint health and make no claim about data age.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zerogex/apis/zerogex-api.md) · [All operations](https://skmtc.dev/zerogex/apis/zerogex-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zerogex/apis/zerogex-api/revisions/03b8b80a6cd5?raw)