Get late-breaking injury / availability for an event (Beta)
Beta. Structured player injury and availability status for an upcoming event, written by an automated monitoring pipeline that watches for late-breaking status changes. Beta coverage: NFL and MLB (more sports rolling out). NFL monitoring starts ~4.5 days before kickoff (Wednesday/Thursday practice reports); MLB stays on a 48-hour window. Checks run on a hours-to-start cadence and also when a main-market line moves ≥20 American-odds points or ≥1.0 spread/total point, plus a guaranteed pre-kickoff confirmation per sport. Subscribe to webhook event_type=injury for material/critical status changes (info reconfirms never fire). available:false is free. No in-game feed.
Request
- Base URL: https://lumify.ai
- URL: https://lumify.ai/v1/events/{event_id}/injuries
- Auth: HTTP bearer
Path parameters
Lumify event ID
Query parameters
Comma-separated injury statuses to drop from the response, e.g. exclude_status=ir to hide injured-reserve/long-term-IL rows (long-standing roster designations, not late-breaking news — these rows are also the most likely to have body_part=null, since roster/depth-chart sources report a designation + return-eligibility date rather than injury details). Does not affect available or X-Credits-Used, which reflect whether the monitor has written any report at all. Valid values: available, day_to_day, doubtful, ir, out, probable, questionable, suspended.
Response
Beta. Per-player status rows plus watch-queue timestamps. If the monitor has not yet written a report, returns 200 with available=false and is NOT charged (X-Credits-Used: 0).
Changes
No recorded changes to this operation across all 1 revision of this API.