For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sidelined

✅ Included in All Plans

The sidelined include is included at no additional cost.

Plans differ only in leagues and API call limits.

Compare plans →

The sidelined include returns injury and suspension records for players linked to a fixture, enriched with start date, end date, games missed, and the specific injury or suspension type.

When to use this

Use the sidelined include when you need to show which players are unavailable for a fixture, build a pre-match injury report, or filter rumour and transfer data by a player's current fitness status. It is the correct data source for any question about whether a named player is available to play.

Sidelined records are not available as a standalone endpoint. They are accessible as an include on the fixtures and teams endpoints.

Retrieving sidelined data

From a fixture

Use this when you need to show which players are unavailable for a specific match.

GET https://api.sportmonks.com/v3/football/fixtures/{{fixtureId}}
?api_token={{apiToken}}&include=sidelined.sideline;sidelined.player;sidelined.type

From a team

Use this when you need a team's current injury and suspension list independent of any fixture.

GET https://api.sportmonks.com/v3/football/teams/{{teamId}}
?api_token={{apiToken}}&include=sidelined.player;sidelined.type

The includes available differ depending on the access point. From a fixture you can chain sideline, participant, fixture, player and type. From a team you can chain player, type, team and season.

Full historical record

The sidelinedHistory include, available on the teams endpoint only, returns every unavailability period for every player at the club, including periods that have already been resolved. Useful for building injury history profiles or filtering by player.

The field shape of sidelinedHistory is identical to sidelined.

Understanding the response

The flat sidelined include returns one object per unavailable player:

With the nested includes, each object expands to include the full sideline record, player profile, and type definition:

Field reference

Sidelined record (top level)

Field
Description
Type

id

Unique ID of this sidelined fixture record.

integer

fixture_id

The fixture this record is attached to.

integer

sideline_id

References the underlying sideline entity containing dates and games missed.

integer

participant_id

The team ID the player belongs to in this fixture.

integer

player_id

The player who is unavailable.

integer

type_id

The injury or suspension type ID. Resolve via the type include or the types endpoint.

integer

Nested sideline object

Field
Description
Type

category

Broad category: injury or suspension.

string

start_date

Date the player was ruled out, in YYYY-MM-DD format.

string

end_date

Expected or actual return date, in YYYY-MM-DD format. Null if unknown.

string / null

games_missed

Number of fixtures missed during this sideline period.

integer

completed

Whether the sideline period has ended. true means the player has returned or the period closed.

boolean

team_id

The team the player was registered to during this period.

integer

season_id

The season the sideline record is associated with. Null if not season-scoped.

integer / null

Nested type object

Field
Description
Type

id

The type ID. Matches type_id on the sidelined record.

integer

name

Human-readable name, e.g. Hamstring Injury, Back Injury.

string

code

URL-safe code, e.g. hamstring-injury.

string

developer_name

Stable machine-readable identifier, e.g. HAMSTRING_INJURY.

string

model_type

Always injury_suspension for sidelined types.

string

Retrieving all injury and suspension types

Use the Injuries and suspensions types reference to look up type IDs, names, codes and developer_name values.

To refresh the catalogue from the API, retrieve all pages of GET All Types:

Increment page until pagination.has_more is false, then keep the rows whose model_type is injury_suspension. In the 15 October 2026 check, the entities endpoint omitted these types and the typesByModelType filter on the Core Types endpoint returned mixed model types. Do not treat either response alone as a complete injury/suspension catalogue.

Common pitfalls

Using the flat include and expecting dates. The flat sidelined include does not return start_date, end_date or games_missed. Those fields live on the nested sideline object. Always chain sidelined.sideline when dates or games missed are needed.

Treating completed: true as current. A completed value of true means the sideline period is over, not that the player is still out. On a past fixture, a completed: true record means the player returned before or by the time that fixture was played. For a pre-match context, check whether end_date is in the future relative to the fixture date.

Expecting sidelined data on every fixture. Sidelined records are populated based on injury and suspension reporting. Fixtures in lower leagues or early in the data coverage window may return an empty sidelined array. An empty array means no records are available, not that all players are fit.

Last updated

Was this helpful?