---
title: "Api V2 Signals Advanced Eod-Pressure Get"
method: GET
path: "/api/v2/signals/advanced/eod-pressure"
tags: ["Trade Signals (v2)"]
---

# Api V2 Signals Advanced Eod-Pressure Get

`GET /api/v2/signals/advanced/eod-pressure`

## 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/eod-pressure`
- Auth: HTTP bearer

End-of-day close pin/drift forecast for the last ~75 minutes of the session.

Combines (a) modeled dealer charm exposure near spot, (b) a
regime-conditional pin/directional house heuristic,
and (c) an OpEx/quad-witching calendar amplifier into a directional close forecast.

**Active window: 14:30–16:00 ET only.** Outside this window the endpoint returns
`score = 0` and `time_ramp = 0` — treat as an "inactive" state, not neutral.

**Logic highlights** (`src/signals/advanced/eod_pressure.py`):
- `time_ramp` — 0 before T-90min, 1.0 by T-15min, linear in between.
- `charm_score = tanh(charm_at_spot / 20M)` over strikes within the ATM band.
- Non-negative GEX: `pin_component = clip(pin_distance_pct / 0.3%)`
  (target attraction heuristic).
- Negative GEX: `pin_component = clip(trailing_signed_return / 0.3%)`
  (amplifies causal recent direction; target distance does not set direction).
  Missing direction or invalid GEX is neutral. These cutoffs are not calibrated.
- `score = (0.6·charm + 0.4·pin) × calendar_amp × time_ramp`;
  `calendar_amp` is 1.5× OpEx, 2.0× quad-witching.

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

**Returns:**
```json
{
  "score": 48.1,
  "direction": "bullish",
  "clamped_score": 0.48, "weighted_score": 0.096, "weight": 0.20,
  "charm_at_spot": 12850000.0,
  "pin_target": 676.0,
  "pin_distance_pct": 0.00042,
  "gamma_regime": "positive",
  "time_ramp": 0.76,
  "calendar_flags": {"opex": false, "quad_witching": false},
  "context_values": {"...atm_band_pct, pin_source, calendar_amp, ..."},
  "score_history": [{"score": 48.1, "timestamp": "..."}, "...up to 90"]
}
```

- `score` — [-100, +100]; positive = bullish close bias, negative = bearish.
- `direction` — `"bullish"` | `"bearish"` | `"neutral"`.
- `charm_at_spot` — signed dollar-delta of dealer charm in the ±ATM band.
- `pin_target` — heavy-GEX strike, or `max_pain` as fallback.
- `pin_distance_pct` — (pin − spot) / spot; signed; typically ±2%.
- `gamma_regime` — `"positive"` | `"negative"` (flips pin-gravity direction).
- `time_ramp` — [0, 1]; scaling ramp toward close.
- `calendar_flags` — booleans for `opex` and `quad_witching`.

**Trader interpretation:**
- `time_ramp > 0.5` + `score > 50` → strong upside pin; trade drift toward `pin_target`.
- `quad_witching = true` doubles the amplifier; treat `|score| > 60` as high-conviction.
- Render an "Inactive — EOD window opens at 14:30 ET" state when `time_ramp == 0`.

**Page design.** Horizontal close-bias bar (-100..+100). Show `pin_target` vs spot
on a small price axis with distance labeled. Badge for OpEx/quad-witching.
Greyed-out card when `time_ramp == 0`.

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