---
title: "Api V2 Signals Advanced Squeeze-Setup Get"
method: GET
path: "/api/v2/signals/advanced/squeeze-setup"
tags: ["Trade Signals (v2)"]
---

# Api V2 Signals Advanced Squeeze-Setup Get

`GET /api/v2/signals/advanced/squeeze-setup`

## 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/signals/advanced/squeeze-setup`
- Auth: HTTP bearer

Squeeze-setup detector — directional flow z-scores correlated with momentum.

Detects bullish/bearish squeeze setups by correlating directional flow z-scores
with momentum acceleration and dealer-gamma posture. Standalone event detector,
not part of the MSI composite.

**Logic highlights** (`src/signals/advanced/squeeze_setup.py`):
- Bullish: `call_flow_z × tanh_scaled(momentum) × momentum_strength × 1.2 (if accelerating)
  × (1.0 if above flip else 0.6) × (1.0 if net_gex < 0 else 0.5)`.
- Bearish: symmetric using `put_flow_z`.
- **Triggered when `|score| ≥ 25` (clamped 0.25).**
- Dead-VIX regime (`vix_level < 15`) attenuates strength ~50%.

**Params:** `symbol` (default `SPY`). Returns 404 when no data exists.

**Returns:**
```json
{
  "score": 38.0, "clamped_score": 0.38, "direction": "bullish",
  "triggered": true,
  "signal": "bullish_squeeze",
  "call_flow_delta": 125000.0, "put_flow_delta": -45000.0,
  "call_flow_z": 2.1, "put_flow_z": -0.8,
  "momentum_z": 1.4,
  "vix_regime": "normal",
  "context_values": {"...momentum_5bar, momentum_10bar, accel_up, accel_dn, net_gex, gamma_flip, flow_norm_used..."},
  "score_history": [{"score": 38.0, "timestamp": "..."}, "...up to 90"]
}
```

- `score` — [-100, +100].
- `signal` — `"bullish_squeeze"` | `"bearish_squeeze"` | `"none"`.
- `triggered` — `true` when `|score| ≥ 25`.
- `call_flow_z` / `put_flow_z` — z-scores; typically [-5, +5].
- `vix_regime` — `"dead"` | `"normal"` | `"elevated"` | `"panic"` | `"unknown"`.

**Trader interpretation:**
- `signal == "bullish_squeeze"` + `accel_up == true` + price above gamma flip
  + `net_gex < 0` → classic short-gamma squeeze; long call spreads.
- `vix_regime == "dead"` → cut conviction; dead-vol regimes lack squeeze fuel.
- `momentum_z` vs flow z-scores divergence: flow without price = early signal;
  price without flow = exhausted move.

**Page design.** Signal pill (bullish/bearish/none) with `triggered` as a bright dot.
Paired bar showing `call_flow_z` and `put_flow_z`. VIX regime chip (color-coded).

## Query parameters

- `symbol` string

## Response `200`

Successful Response

- EnvelopeAny
  - `data` unknown, 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)