---
title: "Admin Event Intelligence"
method: GET
path: "/admin/events/{event_id}/intelligence"
tags: ["admin"]
---

# Admin Event Intelligence

`GET /admin/events/{event_id}/intelligence`

## Request

- Base URL: `https://lumify.ai`
- URL: `https://lumify.ai/admin/events/{event_id}/intelligence`
- Auth: none declared

Return the exact same payload as GET /v1/events/{id}/intelligence.

Used by the admin sports schedule page so the intel modal reflects what
API clients actually receive, rather than a raw DB snapshot.
Requires admin session auth — no API key needed.

``?bookmaker=`` overlays a different book's live prices for legacy
(points-engine) sports. For predictive-framework leagues (currently MLS)
the param is ignored — assessments are priced only against the system
default book, and overlaying a different book's quote would disagree with
the published probability / fair_price.

Delegates to _fetch_intelligence_payload rather than re-implementing the
query/formatting logic — a hand-maintained duplicate here is exactly what
previously let this route hardcode the tennis/default signal schema for
every sport (see _signal_schema_for's docstring) and would otherwise show
a stale lumify_match_confidence view for predictive-migrated leagues
(e.g. MLS) instead of lumify_assessments.

## Path parameters

- `event_id` integer, required

## Query parameters

- `bookmaker` string, nullable

## Response `200`

Successful Response

- unknown

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