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

# Api V2 Signals Basic Get

`GET /api/v2/signals/basic`

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

Latest snapshot of all six Basic Signals in a single round-trip.

Basic Signals are continuous directional reads (clamped to `[-1, +1]`,
scaled to `[-100, +100]`) that complement the 6 MSI components and 6
Advanced Signals. They do **not** contribute to the composite MSI
(weight=0). Each entry is the most recent row persisted to
`signal_component_scores` by `BasicSignalEngine` each cycle.

Use this to populate a dashboard overview without firing six separate
requests. Click-through to the individual `/api/signals/basic/{name}`
endpoint for signal-specific decomposition and history.

**Signals (6, fixed order):** `tape_flow_bias`, `skew_delta`,
`vanna_charm_flow`, `dealer_delta_pressure`, `gex_gradient`,
`positioning_trap`.

**Params:**
- `symbol` (default `SPY`).

**Returns:**
```json
{
  "underlying": "SPY",
  "signals": {
    "tape_flow_bias":        {"score": 28.4,  "clamped_score": 0.284,  "direction": "bullish", "timestamp": "2026-04-22T18:55:00Z", "context_values": {...}},
    "skew_delta":            {"score": -12.7, "clamped_score": -0.127, "direction": "bearish", "timestamp": "...", "context_values": {...}},
    "vanna_charm_flow":      {"score": 0.0,   "clamped_score": 0.0,    "direction": "neutral", "timestamp": "...", "context_values": {...}},
    "dealer_delta_pressure": {"score": 45.1,  "clamped_score": 0.451,  "direction": "bullish", "timestamp": "...", "context_values": {...}},
    "gex_gradient":          {"score": -8.3,  "clamped_score": -0.083, "direction": "bearish", "timestamp": "...", "context_values": {...}},
    "positioning_trap":      null
  }
}
```

- `signals[name]` — `null` when the signal has never persisted a row
  for this symbol (first-deployment case). Render `"—"` in the UI, not `0`.
- `signals[name].score` — `clamped_score × 100`; `[-100, +100]`; 2 decimals.
- `signals[name].clamped_score` — raw `[-1, +1]`.
- `signals[name].direction` — `"bullish"` | `"bearish"` | `"neutral"` (sign of score).
- `signals[name].timestamp` — ISO-8601 UTC of the engine cycle.
- `signals[name].context_values` — signal-specific inputs/derived fields;
  same keys as the per-signal endpoint.

**Trader interpretation.**
- **All six aligned** (same sign) → high-conviction regime; follow the direction.
- **Flow side** (`tape_flow_bias`, `positioning_trap`) **diverging from structure**
  (`gex_gradient`, `vanna_charm_flow`) → potential reversal; flow leads structure intraday.
- **`0.0` during market hours** → signal *abstained* (below its data threshold),
  not "neutral conviction." Don't treat as a bearish read.

**Page design.** Six KPI tiles in a 3×2 grid. Each tile: direction chip
(green/red/gray), large `score` number, signal label. Click-through to
the `/api/signals/basic/{name}` detail view. Null tiles render as `"—"`.
Poll this endpoint together with `/basic/confluence-matrix` at cycle cadence.

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