> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/sidelined.md). # 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 →](https://www.sportmonks.com/football-api/plans-pricing/) 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. ```http 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. ```http 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. ```http GET https://api.sportmonks.com/v3/football/teams/{{teamId}} ?api_token={{apiToken}}&include=sidelinedHistory.type ``` The field shape of `sidelinedHistory` is identical to `sidelined`. ### Understanding the response The flat `sidelined` include returns one object per unavailable player: ```json { "id": 1289943, "fixture_id": 19427671, "sideline_id": 760662, "participant_id": 9, "player_id": 37286732, "type_id": 535 } ``` With the nested includes, each object expands to include the full sideline record, player profile, and type definition: ```json { "id": 1289943, "fixture_id": 19427671, "sideline_id": 760662, "participant_id": 9, "player_id": 37286732, "type_id": 535, "sideline": { "id": 760662, "player_id": 37286732, "type_id": 535, "category": "injury", "team_id": 9, "season_id": null, "start_date": "2025-12-17", "end_date": "2026-02-06", "games_missed": 11, "completed": true }, "player": { "id": 37286732, "common_name": "O. Bobb", "display_name": "Oscar Bobb", "image_path": "https://cdn.sportmonks.com/images/soccer/players/12/37286732.png", "position_id": 27, "date_of_birth": "2003-07-12" }, "type": { "id": 535, "name": "Hamstring Injury", "code": "hamstring-injury", "developer_name": "HAMSTRING_INJURY", "model_type": "injury_suspension", "stat_group": null } } ``` ### 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](https://docs.sportmonks.com/v3/definitions/types/injuries-and-suspensions) 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: ``` GET https://api.sportmonks.com/v3/core/types?api_token={{apiToken}}&per_page=50&page=1 ``` 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. Interpreting completed relative to a past fixture. A completed: true value means the absence period is closed in the current record. It does not prove that the player had returned before a historical fixture. Compare the absence dates with the fixture date, inspect the fixture-linked record, and allow for retrospective updates. A null end\_date means the return date is unknown; it is not, by itself, proof of current unavailability. **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. ### Related * [Fixtures](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/fixtures) * [GET Fixture by ID](/v3/welcome/welcome.md) * [GET All Fixtures](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/fixtures/get-all-fixtures) * [Types](https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/types) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/sidelined.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.