Availability designations as they stood at an instant
The availability designations in force at as_of, one row per athlete, each as an interval with the instant we observed it.
FORWARD-ONLY, AND THAT IS A CORRECTNESS LIMIT RATHER THAN A SCOPE ONE. Before this log existed we kept one row per athlete and overwrote it, so the prior states were not retained and cannot be reconstructed. The log therefore has a floor: the instant observation began. An as_of below it is refused, never answered. meta.floor_means says so in every response.
change_kind keeps three states apart that a caller must be able to distinguish: seeded is the state when observation began, so anything earlier is UNKNOWN rather than absent; listed and revised are observed designations; withdrawn means the athlete is no longer listed, with no designation attached, which is how a recovery reaches you.
open_interval: true means no end was OBSERVED. It is deliberately not called "current": the two differ the moment publishing stops, and observed_at lets you see how old the designation is.
Request
- Base URL: https://api.bigballsdata.com
- URL: https://api.bigballsdata.com/v1/as-of/injuries
- Auth: one of:
- API key in header x-api-key
- HTTP bearer
Query parameters
The instant to read designations as of, RFC3339. REQUIRED and has no default.
The sport to read. Coverage differs per sport; call /v1/as-of/coverage?relation=player_availability for the observed windows.
Response
ok. { data, meta }, with meta.as_of_floor, meta.floor_means and meta.empty_means.
Changes
No recorded changes to this operation across all 3 revisions of this API.