--- title: "Api V2 Gex Pin-Stability Get" method: GET path: "/api/v2/gex/pin-stability" tags: ["GEX (v2)"] --- # Api V2 Gex Pin-Stability Get `GET /api/v2/gex/pin-stability` ## 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/pin-stability` - Auth: HTTP bearer How stable the Pin Strike has been across the current session. Kept off ``/api/gex/summary`` on purpose: that endpoint is a single-row read on a hot cached path, and folding a whole-session scan into it would make every chart poll pay for a figure that changes at most once a minute. 404 when the session carries no active pin at any point — the client then shows nothing rather than a zeroed record. ## Query parameters - `symbol` string ## Response `200` Successful Response - EnvelopePinStabilityResponse - `data` PinStabilityResponse, required: What the Pin Strike has *done* during the session. The third question in the reading order — regime, then confidence, then stability — and the only one the API could not previously answer. A pin that has held one strike since the open and a pin that has migrated thirty points are different signals wearing the same label; without this a drifting pin reads as a level that failed rather than one tracking a repricing book. ``current_*`` is the pin standing right now, ``held_*`` the most recent value that has SETTLED, and ``current_established`` says whether they are the same. Migration is measured between settled levels only, so a one-sample tick at the bell is not reported as a move; ``net_migration`` is signed (negative = the pin has walked down). Sample counts, not minutes: the analytics cycle is ~60s but is not guaranteed to be, so the honest unit is "stored frames". Null-bodied (``stability`` omitted) when the session carried no active pin at all — hide, don't zero. - `symbol` string, required - `current_pin` number, required - `current_since` string, date-time, required - `current_samples` integer, required - `current_established` boolean, required - `held_pin` number, required - `held_since` string, date-time, required - `held_samples` integer, required - `session_open_pin` number, required - `net_migration` number, required - `distinct_values` integer, required - `quiet_samples` integer, required - `total_samples` integer, 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)