---
title: "Get Expiry Rolloff"
method: GET
path: "/api/gex/expiry-rolloff"
tags: ["GEX"]
---

# Get Expiry Rolloff

`GET /api/gex/expiry-rolloff`

## 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/expiry-rolloff`
- Auth: HTTP bearer

Dealer gamma grouped by expiration — what leaves, and when.

The nearest tranche is the single largest *scheduled* change to the
surface and the one thing a same-day snapshot cannot show: at its close
that gamma stops existing whether or not anybody trades.  A trader who
knows 38% of the book expires tonight reads tomorrow's map differently.

``share`` is computed on ABSOLUTE gamma so an internally offsetting
tranche (a big call wall against a big put wall) still reads as large —
all of it is leaving, and the offset does not survive the expiry.

"Is that a lot?" is answered by ``context``: the percentile of today's
share against this symbol's stored sessions, plus the plain word for it.
Until enough sessions are stored, ``percentile`` is null and the raw
share stands on its own — which is still interpretable, just not ranked.

## Query parameters

- `symbol` string
- `max_tranches` integer
- `strike_limit` integer

## Response `200`

Successful Response

- unknown

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