Skip to main content

Endpoint

Top-level, like the sessions catalog. The rows are scheduled games, not sessions — access can be granted on a game before any feed exists for it, and this endpoint is where those grants surface: your schedule of covered games, soonest first. There is nothing to subscribe to yet; when coverage goes live, the session appears in GET /api/sessions carrying the same gameId, and every feed URL comes from that session row. A game leaves this list when its scheduled window has fully passed, whether or not a session ever covered it.

Authentication

Same as the sessions catalog: a valid ss_ API key or JWT as a Bearer token or ?token=, no anonymous tier. The list is exactly the games your account was granted — there is no public slice here.

Error responses


Response

Ordering is soonest first (scheduledStart ascending).

Polling pattern

Poll this beside GET /api/sessions?status=open and key both by gameId: a game in this list with no matching open session is scheduled; once an open session shares its gameId, that session row is the live one (subscribe with its sessionId), and this list drops the game shortly after its window passes.