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

# Api V2 Gex Regime-Series Get

`GET /api/v2/gex/regime-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/regime-series`
- Auth: HTTP bearer

The Gamma Shift read at every 5-minute bar of a session.

Where ``/api/gex/regime-shift`` answers "how did dealer gamma change
between these two moments" as a single card, this is the same maths as a
line — so structure can sit on the same timeline as
``/api/flow/hedging`` and be read against it. Flow says how hard the tape
is pushing; this says whether the book absorbs or amplifies it.

Two lenses per bar. ``anchored_*`` is versus the session's first bar
("changed today"), the counterpart of the flow panel's cumulative curve.
``rolling_*`` is versus ``rolling_bars`` bars back ("changing right now"),
the counterpart of the rate line and the one to read beside a flip. They
do not sum: both weight strikes by proximity to each bar's OWN spot, so
the kernel re-centres every bar.

Positive ``stability`` means more long gamma near spot — dealers hedge
against moves, so the tape pins. Negative means the book has turned
accelerant. Positive ``lean`` means the change is supportive; negative
means capping.

Scores are RAW dollar-GEX; normalising against a trailing distribution of
sessions is ``/api/gex/regime-history``'s job.

Served from a table the Analytics Engine materialises one bar at a time.
Computing it on read would mean diffing two ~1500-row chains per bar per
viewer per poll — the shape that took the strike-profile timeseries down
in Aug 2026 — so a miss returns empty rather than falling back to compute.

Each bar also carries the spot-to-flip cushion: how much room price has
before the gamma regime itself changes. The flip level and the typical
30-minute move are stored; distance, direction, the rolling rate and the
SECURE / NORMAL / THIN / CROSSING label are derived here, so retuning a
threshold reclassifies history instead of leaving old bars labelled by a
rule that is no longer live. The label is never computed from raw points,
because ten points is a crossing risk on SPX and a comfortable cushion on
SPY: it grades the cushion against the typical 30-minute realized move
(``cushion_basis='move_30m'``), and falls back to a fraction of spot, which
has no NORMAL band, only where no move was stored (``'spot_fraction'``).
``cushion_state`` of ``NO_FLIP`` means the gamma profile had no zero
crossing at all, which is a different statement from a distant one.

Same session resolution as ``/api/flow/hedging``, so the two cover
identical bars. Rows newest → oldest. Unknown symbols 404; a session with
nothing written yet returns an empty ``bars`` list.

## Query parameters

- `symbol` string, required
- `session` 'current' | 'prior'
- `date` string, nullable: An explicit ET trading day, YYYY-MM-DD. Overrides `session`. gamma_regime_5min has been written per bar since this panel shipped and is retention-exempt, so any stored session answers. A day with nothing written returns 200 with an empty `bars` list -- never 404.
- `intervals` integer, nullable: If provided, return only the last N 5-minute bars (tail window).

## Response `200`

Successful Response

- EnvelopeGammaRegimeSeriesResponse
  - `data` GammaRegimeSeriesResponse, required: Intraday dealer-gamma structure across a session. Shares ``/api/flow/hedging``'s session window and 5-minute grid, so the two stack into one timeline: flow says how hard the tape is pushing, this says whether the book absorbs or amplifies it.
    - `symbol` string, required
    - `session` string, required
    - `rolling_bars` integer, nullable
    - `bars` GammaRegimeBar[], required
      - `timestamp` string, required
      - `bar_start` string, required
      - `bar_end` string, required
      - `spot` number, nullable
      - `anchored_lean` number, required
      - `anchored_stability` number, required
      - `anchored_net_shift` number, required
      - `anchored_gross_shift` number, required
      - `rolling_lean` number, nullable
      - `rolling_stability` number, nullable
      - `rolling_net_shift` number, nullable
      - `rolling_gross_shift` number, nullable
      - `sigma_price` number, nullable
      - `near_spot_stock` number, nullable
      - `strike_count` integer, required
      - `expired_expirations` string[]
      - `rolling_bars` integer, nullable
      - `gamma_flip` number, nullable
      - `flip_distance_pts` number, nullable
      - `flip_distance_frac` number, nullable
      - `cushion_pts` number, nullable
      - `cushion_side` string, nullable
      - `cushion_step_pts` number, nullable
      - `cushion_rate_pts` number, nullable
      - `cushion_accelerating` boolean, nullable
      - `cushion_state` string, nullable
      - `cushion_move_ratio` number, nullable
      - `cushion_basis` string, nullable
      - `cushion_rate_context` string, nullable
      - `typical_move_30m` number, nullable
      - `cushion_summary` string, nullable
  - `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)