Monitor player availability for an upcoming event

What this is (and is not)

Lumify’s wedge is per-event monitoring with severity, odds-move triggers, and agent webhooks — Beta NFL and MLB.

How the monitor runs

1. Resolve an upcoming event (list_events / query_events / get_event).
2. The monitor starts watching inside a sport-specific pre-kickoff window (below).
3. Each check may write or refresh structured rows on GET /v1/events/{id}/injuries.
4. available: false means no first report yet — not charged.
5. Material/critical transitions can also fire a signed webhook (event_types includes injury).

Cadence (Beta)

Webhook payload trigger is one of cadence / odds_move / checkpoint / early_report when a delivery fires. early_report is the NFL Wednesday/Thursday practice-report snap (T-96h / T-72h).

REST — first call

Instant trial key (no signup): /docs/ai. Persistent key: /register.

# 1) Find an upcoming NFL or MLB event
curl "https://lumify.ai/v1/events?sport=nfl&status=scheduled&limit=5" \
  -H "Authorization: Bearer YOUR_API_KEY"

# 2) Pull injury / availability for that event
curl "https://lumify.ai/v1/events/{id}/injuries" \
  -H "Authorization: Bearer YOUR_API_KEY"

# Optional: drop long-term IR / IL roster designations
curl "https://lumify.ai/v1/events/{id}/injuries?exclude_status=ir" \
  -H "Authorization: Bearer YOUR_API_KEY"

Always 200 when the event exists. Read available before trusting injuries[]. 404 only if the event ID does not exist. available: false → X-Credits-Used: 0.

Inspector: API reference — event injuries.

MCP — get_injuries

Hosted MCP: https://lumify.ai/mcp (Bearer). Tool: get_injuries. Credits match REST (0 when available: false). Setup: /docs/ai · landing: /sports-mcp-server.

{
  "mcpServers": {
    "lumify": {
      "url": "https://lumify.ai/mcp",
      "headers": { "Authorization": "Bearer lmfy-YOUR_KEY" }
    }
  }
}

Agent prompt pattern (illustrative): “For event {id}, call get_injuries. If available is false, wait or poll later. Summarize players with status out/doubtful/questionable and any previous_status changes. Do not invent rows.”

Field catalog

Inspector fields and the full sample live on GET /v1/events/{id}/injuries. The tables below are the how-to subset.

Envelope

injuries[] row

Severity (read this before wiring alerts)

exclude_status

Comma-separated, case-insensitive statuses to drop from injuries[] (e.g. exclude_status=ir). Useful to hide injured-reserve / long-term IL roster designations (not late-breaking news). Those rows also most often have body_part: null. Unknown values → 400. Filtering every row out does not flip available to false if the monitor has data; credits unchanged by filter alone.

Webhook recipe — push on material/critical only

curl -X POST https://lumify.ai/v1/webhooks \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/hooks/lumify",
    "event_types": ["injury"],
    "sport": "nfl"
  }'

Or scope to one event with "event_id": 19190 instead of sport.

Behavior (Beta): one signed POST per player-status transition at material or critical severity. Info reconfirms never fire. Deduped via notified_at so the same transition is not re-sent. Delivery data carries player, team, status, previous_status, severity, hours_to_start, and trigger (cadence / odds_move / checkpoint / early_report). 0.5 credits per delivery.

Verify signatures with the signing_secret returned once on create — see webhooks in the API reference. Polling get_injuries remains valid when you do not want push.

Agent loop (copy-paste intent)

1. list_events / query_events → pick event_id (NFL or MLB, upcoming).
2. get_injuries → if available is false, backoff until next_check_at or poll on a coarse cadence.
3. Prefer rows where severity is material or critical, or where previous_status is non-null.
4. Optionally register webhook event_types: ["injury"] for the sport or event.
5. Join player_id to props / intelligence on the same event ID when you need line context — do not scrape a second ID space.
6. Never present status tags as betting advice.

Example response

{
  "event_id": 19190,
  "available": true,
  "last_checked_at": "2026-09-03T21:07:00Z",
  "confirmed_at": null,
  "next_check_at": "2026-09-03T21:22:00Z",
  "injuries": [
    {
      "player": "Patrick Mahomes",
      "player_id": 44012,
      "team": "Kansas City Chiefs",
      "team_id": 18,
      "status": "questionable",
      "previous_status": null,
      "body_part": "ankle",
      "note": "Listed as questionable on the Friday injury report.",
      "source_url": "https://www.nfl.com/injuries",
      "severity": "info",
      "last_changed_at": "2026-09-03T21:07:00Z"
    }
  ]
}

Illustrative shape — first sighting of a routine questionable is info (no webhook). A later change to out / doubtful would be material (or critical inside 6 hours of kickoff). Always verify against a live event ID.

FAQ

Limits (frank)

• Beta — NFL + MLB windows above; more sports rolling out.
• No in-game injury feed after kickoff/first pitch.
• Not a guaranteed-complete official report; rows are structured extractions with source_url when captured.
• Unmatched names keep the player string with null player_id.

Related

• API reference — event injuries
• Guides — MCP tools
• Sports MCP Server
• AI-assisted setup / instant key
• Player props catalog
• Understanding odds
• Sports coverage