---
title: "Get Signal Trailing Record"
method: GET
path: "/api/scorecard/signal-record"
tags: ["Scorecard"]
---

# Get Signal Trailing Record

`GET /api/scorecard/signal-record`

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

Per-signal flip record over the last ``sessions`` trading days.

The daily scorecard is one calendar day, which cannot answer "is this
signal any good" — the question a subscriber actually asks after a signal
calls one session correctly. This is the same flip definition and the same
session-bounded forward return, aggregated over a window.

**Params:**
- ``symbol`` — underlying (default ``SPY``).
- ``sessions`` — trailing weekdays to cover (2–120, default 30).
- ``horizon_minutes`` — forward window (5–240, default 60).
- ``signal`` — one signal name; omit for all of them.

**Returns:** ``signals[]`` with ``flips``, ``scored``, ``wins``,
``losses``, ``win_rate`` and ``avg_directional_return`` per name.

``scored`` can be lower than ``flips``, and ``win_rate`` is ``null`` when
nothing was scorable. A signal that only fires near the close
(``eod_pressure``) can have many flips and few scorable ones; that is the
honest shape of the measurement, not a defect to paper over.

## Query parameters

- `symbol` string
- `sessions` integer
- `horizon_minutes` integer
- `signal` string, nullable: Single signal name; omit for every Basic + Advanced signal.

## Response `200`

Successful Response

- unknown

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