Api V2 Flow Hedging Sessions Get

Trading days that have a stored Hedging Flow session, newest first.

The index behind /api/flow/hedging?date=. Deliberately a list of days that HAVE data rather than a date picker over the calendar: a picker invites a reader onto an empty session and lets them conclude the feature is broken, which is why /api/replay/sessions and the scorecard's equivalent are both shaped this way.

Read from hedging_flow_5min and nothing else. Listing from the live tables instead would advertise exactly the days the prune window keeps and hide every older session that is still perfectly readable -- the list and the permalinks have to agree about which days exist.

Each entry carries enough to render a card rather than a date: how many bars the day has, how many of those were real rather than carried forward, whether a 0DTE scope exists for it, and where the session's cumulative lean finished.

has_more comes from asking the database for one row more than the caller wanted and then dropping it. That extra row is what lets the answer be certain instead of inferred: a caller comparing count to limit is wrong exactly when the total is a multiple of the page size, and it offers the reader a next page that renders as an empty archive.