---
title: "Api V2 Scorecard Daily Get"
method: GET
path: "/api/v2/scorecard/daily"
tags: ["Scorecard (v2)"]
---

# Api V2 Scorecard Daily Get

`GET /api/v2/scorecard/daily`

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

One trading day's aggregate of the engine's output.

Combines three reads — persisted Action Cards, per-signal flip events
with realized return at ``horizon_minutes``, and the closing MSI regime —
into a single payload sized for the public ``/scorecard/{date}`` page
and the auto-tweet job.

**Params:**
- ``date`` — YYYY-MM-DD; defaults to today in America/New_York.
- ``symbol`` — underlying (default ``SPY``).
- ``horizon_minutes`` — forward window for ``realized_return`` (5–240, default 60).
  The forward price is bounded to the same regular session: a flip within
  this many minutes of the close counts in ``flips`` but not in ``scored``,
  and contributes nothing to ``avg_directional_return``. Grading it against
  an after-hours print (or, on a Friday, the next Monday's open) is what
  made ``eod_pressure`` — which can only fire in the last 90 minutes —
  report a meaningless number for every session.

**Returns:**
```json
{
  "date": "2026-06-29",
  "symbol": "SPY",
  "tz": "America/New_York",
  "horizon_minutes": 60,
  "cards": {
    "total": 12,
    "by_action": [{"action": "SELL_CALL_SPREAD", "count": 4}, ...],
    "first_card_id": 4221,
    "first_card_permalink": "/cards/4221",
    "items": [
      {"id": 4221, "timestamp": "2026-06-29T13:42:00+00:00",
       "pattern": "call_wall_fade", "action": "SELL_CALL_SPREAD",
       "tier": "0DTE", "direction": "bearish", "confidence": 0.68,
       "permalink": "/cards/4221"},
      ...
    ]
  },
  "signals": {
    "events": [{"name": "...", "flips": 3, "wins": 2, "losses": 1,
                 "avg_directional_return": 0.0042}, ...],
    "best":  {"name": "squeeze_setup",     "avg_directional_return": 0.0074, "wins": 2, "losses": 1, "flips": 3},
    "worst": {"name": "vanna_charm_flow",  "avg_directional_return": -0.0031, "wins": 1, "losses": 2, "flips": 3}
  },
  "regime": {"timestamp": "...", "composite_score": -0.28, "label": "short gamma"},
  "tweet_text": "SPY · 2026-06-29 — 12 Playbook calls. Best: Squeeze Setup +0.74%. Worst: Vanna Charm Flow −0.31%. Regime: short gamma. https://zerogex.io/scorecard/2026-06-29",
  "is_empty": false
}
```

``tweet_text`` is the canonical one-line summary the auto-tweet job
uses verbatim; computing it server-side keeps wording consistent
across the OG card, the page header, and the X/Discord tweet.

Returns ``is_empty: true`` with zeroed sections when no cards were
emitted and no flip events occurred (typical for non-trading days or
pre-launch dates).

## Query parameters

- `date` string, nullable: Trading day in YYYY-MM-DD; defaults to today (America/New_York).
- `symbol` string
- `horizon_minutes` integer

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