---
title: "Active injury reports"
method: GET
path: "/v1/injuries"
tags: ["injuries"]
---

# Active injury reports

`GET /v1/injuries`

## Request

- Base URL: `https://api.bigballsdata.com`
- URL: `https://api.bigballsdata.com/v1/injuries`
- Auth: one of:
  - API key in header `x-api-key`
  - HTTP bearer

Injury reports by sport. What a row MEANS differs by league, because
injury data is a reporting artifact and leagues differ in what they
compel teams to disclose:

- `american_football`: the NFL's **mandated** weekly injury report
  `status` is a league-defined game designation:
  Out / Doubtful / Questionable. `comment` carries practice
  participation. `player.position` is always present. Published per
  week; `meta.as_of` is the date of the games that week's report covers.
  **No `return_date`**: the NFL report is designation-based and states
  no expected return, so the field is omitted rather than sent as a
  permanent null. Only rows carrying a game designation are returned;
  a player logging a full practice with no designation is not injured,
  and is not listed.
- `basketball`, `ice_hockey`: NBA / NHL reports from a paid aggregator
  (`aggregator-paid`). Note the NHL requires no disclosure at all, so
  NHL detail is vague at the league ("upper-body"), not at this API.
- `football`: soccer absences from a paid aggregator
  (`aggregator-paid`). Mostly
  **retrospective**: a record that a player missed a fixture that has
  been played, which includes non-injury absences such as suspension.
  `meta.as_of` is the newest matchday held.
- `baseball`, and everything else: not served; returns 400 naming the
  sports that are.

Endpoints that serve a stored snapshot always carry `meta.as_of` (the
currency of the DATA, never the time we last ingested it) and set
`meta.stale: true` with a plain-language `meta.message` when no fresher
data exists yet (e.g. between seasons).

## Query parameters

- `sport` string
- `team` string

## Response `200`

ok. `{ data, meta }`; `meta.as_of` is the currency of the DATA. Declared no `content` until 2026-09-25.

- object: The standard response wrapper. Only `data` is guaranteed. `error` is absent (not null) on 16 of 40 live 200 responses measured 2026-09-18, so test for the KEY before reading it; this block declared it required until then. On a non-2xx, `error` is present and `data` is absent.
  - `data` object, required
    - `sport` 'football' | 'basketball' | 'baseball' | 'ice_hockey' | 'cricket' | 'mma' | 'boxing' | 'formula1' | 'american_football'
    - `count` integer: Rows in `injuries` AFTER any ?team= filter, so it is the count of what you were given.
    - `injuries` object[]
      - `player` object
      - `status` string: On american_football this is the NFL's league-defined game designation (Out / Doubtful / Questionable), not a medical status.
      - `injury_type` string, nullable
      - `comment` string, nullable: Practice participation on american_football.
      - `updated_at` string
  - `meta` ResponseMeta: Response metadata. NOTHING here is guaranteed: measured over 38 live envelopes on 2026-09-18, `cached` and `request_id` appeared in 29, `source` in 28, `cache_age_ms` in 9 and `confidence` in 6. This block previously declared all five REQUIRED, which no response has ever satisfied. Treat every field as optional and branch on its absence. Routes add their own keys here (`count`, `limit`, `offset`, `note`, `total`, and per-endpoint ones), so do not assume a closed set.
    - `date_window` object: Present when ?date= was applied. The exact window the filter used, so an omission at a day boundary is visible. start_utc is inclusive, end_utc exclusive. timezone is UTC, or the zone named by ?tz=, in which case the window is that local day. Boxing card dates are published event dates, so timezone and bounds are null there.
      - `date` string
      - `timezone` string, nullable
      - `start_utc` string, date-time, nullable
      - `end_utc` string, date-time, nullable
      - `note` string
    - `source` 'official-league' | 'aggregator-paid' | 'aggregator-free' | 'community-scraper' | 'forecast' | 'mixed' | 'cache' | 'none' | 'unknown-source' | 'stored' | 'catalogue' | 'gateway' | 'coverage-snapshot': Opaque source-tier label. Customers never see the vendor identity. `forecast` marks a weather forecast (GET /v1/matches/{id}/weather).
    - `confidence` number, float
    - `cached` boolean
    - `cache_age_ms` integer
    - `request_id` string
    - `fields_missing` string[]
    - `note` string: Short factual disclosure about something this response deliberately withheld, present only when there is something to disclose. On live scores it appears when `match_id` could not be resolved to a stored match and was therefore omitted: it gives the counts and points at `/v1/stored/matches`, whose ids you can call back into. Absent when every served id resolves. Distinct from `message`, which explains `coverage: false` or a stale response. This one is attached to a response that DID serve data and names the part of it that is deliberately missing.
  - `error` ApiError
    - `code` string, required
    - `message` string, required
    - `details` unknown

---

[API](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api.md) · [All operations](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bigballsdata/apis/big-ball-sports-api/revisions/31fb54ac414e?raw)