What a call returns
One row per player per missed fixture, with the reason as the source states it, joined on the same player_id as every other endpoint. Every response carries meta.as_of and meta.stale, so the age of the data is part of the contract rather than something you infer.
Requestbash
curl "https://api.bigballsdata.com/v1/injuries?league=ligue1" \
-H "Authorization: Bearer $BBS_API_KEY"Questions
- How current is the Ligue 1 data?
- Data runs through 11 October 2026, the most recent Ligue 1 matchday we hold. Every response carries the same date, so you never have to guess how old a record is — read meta.as_of rather than trusting a figure printed on this page.
- Is this an injury report like the NFL publishes?
- No, and it is worth being exact about the difference. The NFL publishes a mandated, forward-looking weekly report. Ligue 1 has no equivalent, so what we hold is an absence record: who missed a match that has already been played, and why. A small share is forward-looking doubt. If you need a pre-match designation, that exists for the NFL at /v1/nfl/injuries and does not exist for European football anywhere.
- Are suspensions and red cards included?
- Yes, and they are labelled rather than hidden. A meaningful minority of absences are not injuries — red and yellow card suspensions, international duty, illness, loan moves. Every record carries the reason as the source states it, so you can filter to injuries alone. We call the dataset absences rather than injuries for exactly that reason.
- How do I join it to the rest of the API?
- On player_id — the same canonical id used by the stat endpoints, the xG leaderboards and the match endpoints. One id, no cross-source mapping.
- Is it on the free tier?
- Yes, on the same free tier as the rest of the API: 250 requests a day, 500 with GitHub connected. No credit card.
Related APIs
Other APIs you can build with: