---
title: "Get Gamma Weather Series"
method: GET
path: "/api/gex/weather-series"
tags: ["GEX"]
---

# Get Gamma Weather Series

`GET /api/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/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

- GammaWeatherSeriesResponse: 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

## 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)