---
title: "Api V2 Signals Basic Positioning-Trap Get"
method: GET
path: "/api/v2/signals/basic/positioning-trap"
tags: ["Trade Signals (v2)"]
---

# Api V2 Signals Basic Positioning-Trap Get

`GET /api/v2/signals/basic/positioning-trap`

## 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/basic/positioning-trap`
- Auth: HTTP bearer

Crowd-positioning trap — squeeze/flush risk from one-way crowding.

Flags setups where tape behavior is starting to invalidate crowd
direction — the classic squeeze/flush patterns.

- **`+score` (squeeze risk):** puts crowded + aggressive put-buying +
  up-momentum + price above gamma flip + short-gamma regime →
  upside squeeze fuel.
- **`−score` (flush risk):** calls crowded + aggressive call-buying +
  down-momentum + price below gamma flip + short-gamma → downside
  air-pocket.

Uses **signed** net smart-money premium (`buy − sell`) from
`flow_contract_facts` when available — more informative than legacy
total_premium because opposite-side buying nets out (a big put-buy
+ big put-sell should *not* count as crowd skew).

**Logic highlights** (`src/signals/basic/positioning_trap.py`):
```
short_crowding = clip((put_call_ratio − 1.05) / 0.35, [0, 1])
long_crowding  = clip((0.95 − put_call_ratio) / 0.35, [0, 1])
put_skew       = max(0, −smart_imbalance)
call_skew      = max(0, +smart_imbalance)

squeeze = 0.45·short_crowding + 0.25·put_skew
        + 0.15·clip(momentum_5bar / 0.004, [0,1])
        + 0.10·above_flip + 0.05·neg_gex
flush   = 0.45·long_crowding  + 0.25·call_skew
        + 0.15·clip(−momentum_5bar / 0.004, [0,1])
        + 0.10·below_flip + 0.05·neg_gex
score   = clip(squeeze − flush, [-1, 1])
```
- `smart_imbalance = (smart_call_net − smart_put_net) / (|call_net| + |put_net|)`,
  abstaining when denominator `< $100K`.

**Params:**
- `symbol` (default `SPY`). Returns 404 if no row exists yet.

**Returns:**
```json
{
  "underlying": "SPY", "timestamp": "...",
  "clamped_score": 0.52, "score": 52.0, "direction": "bullish",
  "weighted_score": 0.0, "weight": 0.0,
  "smart_imbalance": -0.41,
  "smart_imbalance_source": "signed_net_premium",
  "momentum_5bar": 0.0025,
  "context_values": {
    "put_call_ratio": 1.28, "smart_imbalance": -0.41,
    "smart_imbalance_source": "signed_net_premium",
    "momentum_5bar": 0.0025, "close": 577.24,
    "gamma_flip": 574.5, "net_gex": -1.4e9
  },
  "score_history": [{"score": 31.0, "timestamp": "..."}, "...up to 90"]
}
```

- `score` / `clamped_score` — `[-100, +100]` / `[-1, +1]`. `+` = squeeze risk, `−` = flush risk.
- `smart_imbalance` — `[-1, +1]`; `+` = call-buy heavy, `−` = put-buy heavy.
  Counter-intuitively, *put-heavy imbalance* drives `+score` (squeeze fuel).
- `smart_imbalance_source` — `"signed_net_premium"` (best) | `"signed_top_level"` (older fields).
- `momentum_5bar` — 5-bar price %, e.g. `0.0035` = +0.35%.
- `context_values.put_call_ratio` — float, typically `[0.5, 2.0]`.
- `context_values.close` / `gamma_flip` — used to derive `above_flip`/`below_flip`.
- `context_values.net_gex` — signed; `< 0` amplifies both sides.
- `score_history` — up to 90 recent points.

**Trader interpretation.**
- `score > +50` → upside squeeze setup. Long-delta; size up if
  `close > gamma_flip` AND `net_gex < 0`.
- `score < −50` → downside flush setup. Put debit spreads; trim longs.
- Moderate magnitude (±25–50) **plus contradictory `tape_flow_bias`**
  → the trap may already be unwinding; wait.
- `smart_imbalance_source = "signed_top_level"` → lower-precision fields;
  signal still valid.

**Page design.** Horizontal ±100 "trap meter" with "Flush Risk" (left)
and "Squeeze Risk" (right). Decomposition panel showing the five input
factors as mini-bars (short/long_crowding, put/call_skew, momentum,
above/below_flip, neg_gex) so the trader sees *why*. Contextual footer
with `put_call_ratio`, `momentum_5bar %`, `close vs gamma_flip`, `net_gex` sign.

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