---
title: "Api V2 Gex Weather-Series Get"
method: GET
path: "/api/v2/gex/weather-series"
tags: ["GEX (v2)"]
---

# Api V2 Gex Weather-Series Get

`GET /api/v2/gex/weather-series`

## 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/gex/weather-series`
- Auth: HTTP bearer

The session's Gamma Weather history, and the moments it said something new.

``/api/gex/weather`` answers what the panel reads right now. This answers
what happened while nobody was looking, which the header cannot: a word on
a chip captures one slice of time, and someone returning to the page after
two hours is asking about a pattern.

Both endpoints go through the same loader and the same classifier, so a bar
described here and the same bar described there cannot disagree.

``changes`` is not one entry per bar. An entry exists only where a label
actually moved, so a quiet afternoon in one state produces a single line
instead of fifty identical ones, and the trail stays readable at a glance.
Every label is classified causally, from its bar and the ones before it,
so the trail is not a hindsight summary. It is not a recording either: the
session is reclassified on every read, so a bar the panel read while it
was still filling can show a label here that the panel did not.

Same 400 / 404 / 409 semantics as the current-state endpoint.

## Query parameters

- `symbol` string, required
- `session` 'current' | 'prior'
- `date` string, nullable: An explicit ET trading day, YYYY-MM-DD. Overrides `session`, and resolves through the same loader the current-state read uses, so a dated history and a dated header describe the same session.

## Response `200`

Successful Response

- EnvelopeGammaWeatherSeriesResponse
  - `data` GammaWeatherSeriesResponse, required: The session's Weather history, plus only the moments worth commenting on. The current-state endpoint answers "what is it now". This answers "what happened while I was away", which a header cannot: words capture one slice of time and the question is about a pattern. ``changes`` is deliberately not one entry per bar. A quiet stretch produces nothing, so a session that sits in one state all afternoon yields one line rather than fifty identical ones.
    - `symbol` string, required
    - `session` string, required
    - `bars` GammaWeatherBar[], required
      - `bar_start` string, required
      - `state` string, required
      - `label` string, required
      - `sentence` string, required
      - `pressure` string, required
      - `structure` string, required
      - `gamma_trend` string, required
      - `lean_side` string, nullable
      - `cushion` string, required
      - `cushion_band` string, nullable
      - `persistence` string, required
      - `persistence_label` string, required
      - `pressure_reversing_bars` integer
      - `age_bars` integer, required
      - `age_minutes` number, nullable
      - `age` string, nullable
      - `age_label` string, nullable
      - `pending_state` string, nullable
      - `pending_label` string, nullable
      - `pending_bars` integer
    - `changes` GammaWeatherChange[], required
      - `bar_start` string, required
      - `field` string, required
      - `kind` string, required
      - `text` string, required
      - `opening` boolean
    - `confirm_bars` integer, required
    - `basis` string, required
    - `disclosure` string, 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)