---
title: "Api V2 Signals Score-History Get"
method: GET
path: "/api/v2/signals/score-history"
tags: ["Trade Signals (v2)"]
---

# Api V2 Signals Score-History Get

`GET /api/v2/signals/score-history`

## 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/score-history`
- Auth: HTTP bearer

Time series of the composite MSI, newest-first.

**Params:** `underlying` (default `SPY`), `limit` (default 600, max 5000),
`lookback_days` (default 4, max 30). The DB read caps results to the
requested calendar-day window so the default response covers the current
and previous sessions across a normal weekend; raise `lookback_days` to
drive multi-day chart presets (e.g. 5-trading-day view).

**Returns.** An array of objects with `timestamp`, `composite_score`, and
`components` (same shape as `/score`). Rows are ordered by `timestamp DESC`
so index 0 is the most recent. `timestamp` is ISO-8601 UTC of the engine
cycle that produced the row.

```json
[
  {
    "timestamp": "2026-04-22T18:55:00Z",
    "composite_score": 63.42,
    "components": {
      "net_gex_sign":          {"max_points": 16, "contribution":  9.60, "score":  0.6},
      "gamma_anchor":          {"max_points": 30, "contribution": -2.10, "score": -0.07,
                                "context": {"flip_distance_subscore": 0.21,
                                            "local_gamma_subscore": -0.42,
                                            "price_vs_max_gamma_subscore": 0.17}},
      "put_call_ratio":        {"max_points": 12, "contribution":  2.40, "score":  0.2},
      "volatility_regime":     {"max_points":  6, "contribution": -0.08, "score": -0.013},
      "order_flow_imbalance":  {"max_points": 19, "contribution":  6.65, "score":  0.35},
      "dealer_delta_pressure": {"max_points": 17, "contribution":  3.40, "score":  0.2}
    }
  }
]
```

**Page design.** Line chart of `composite_score` over `timestamp` with shaded
regime bands at 20/40/70. Stacked-area chart of component `contribution`
values underneath shows which component flipped the regime.

## Query parameters

- `underlying` string
- `limit` integer
- `lookback_days` integer

## 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/753b26bf0592?raw)