---
title: "Admin Sports Schedule"
method: GET
path: "/admin/sports-schedule"
tags: ["admin"]
---

# Admin Sports Schedule

`GET /admin/sports-schedule`

## Request

- Base URL: `https://lumify.ai`
- URL: `https://lumify.ai/admin/sports-schedule`
- Auth: none declared

Thin wrapper around _admin_sports_schedule_impl so a crash between the
fetch and the final render is still visible (Phase 0 perf-plan hardening —
see the sports-schedule-explorer-perf-plan canvas). The real handler's
own admin.sports_schedule.{fetch,enrich,total} logs only fire on the
happy path; reindenting that whole ~250-line body under a try/finally
to close that gap directly was judged too risky, so the guarantee lives
here instead, one call frame up, where it can't perturb the existing
logic at all.

Phase 1: ``view`` / ``tz_offset`` default to None (param absent) so a
cookie can supply the viewer's last preference before any DB/API work.

## Query parameters

- `sport` string
- `status` string
- `group` string[]
- `week` integer
- `view` string, nullable
- `day` string
- `tz_offset` integer, nullable
- `partial` boolean

## Response `200`

Successful Response

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/lumify/apis/lumify-sports-intelligence-api.md) · [All operations](https://skmtc.dev/lumify/apis/lumify-sports-intelligence-api/llms.txt) · [OpenAPI document](https://skmtc.dev/lumify/apis/lumify-sports-intelligence-api/revisions/f91ea41a2606?raw)