> 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/fixture-includes-reference.md).

# Fixture includes reference

This page documents the response shape for fixture includes that aren't covered by their own dedicated tutorial. Use it alongside the [Fixture entity page](https://docs.sportmonks.com/v3/endpoints-and-entities/entities/fixture) when you need to know exactly what comes back for a specific include.

### Timeline

#### What it returns

`include=timeline` returns a curated subset of in-match events, not the full events feed. Based on live testing, timeline entries currently cover:

| `type_id` | Event           |
| --------- | --------------- |
| 126       | Corner          |
| 569       | Shot On Target  |
| 570       | Shot Off Target |
| 1514      | Offside         |

{% hint style="info" %}
This list reflects what was observed on a single tested fixture and may not be exhaustive across all leagues or match states. If you need the full authoritative list of timeline type\_ids, cross-check against `/core/types` filtered to the types above, or reach out and we'll expand this table.
{% endhint %}

For goals, cards, and substitutions, use the [Events include](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/events) instead, timeline and events are separate, non-overlapping includes.

#### Example response

```json
{
  "id": 157432869,
  "fixture_id": 19714695,
  "period_id": 7032992,
  "participant_id": 73,
  "type_id": 126,
  "section": "timeline",
  "player_id": null,
  "related_player_id": null,
  "player_name": null,
  "related_player_name": null,
  "result": null,
  "info": null,
  "addition": "1st Corner",
  "minute": 12,
  "extra_minute": null,
  "injured": null,
  "on_bench": false,
  "coach_id": null,
  "sub_type_id": null,
  "detailed_period_id": 7032992,
  "rescinded": null,
  "sort_order": 1
}
```

#### Field descriptions

| Field                             | Type         | Description                                                                                                                                                                                          |
| --------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id`                              | integer      | Unique identifier for this timeline entry                                                                                                                                                            |
| `fixture_id`                      | integer      | The fixture this entry belongs to                                                                                                                                                                    |
| `period_id`                       | integer      | The period (half, extra time, etc.) this entry occurred in                                                                                                                                           |
| `participant_id`                  | integer      | The team this entry is attributed to                                                                                                                                                                 |
| `type_id`                         | integer      | The event type, see table above                                                                                                                                                                      |
| `section`                         | string       | Always `"timeline"` for this include                                                                                                                                                                 |
| `player_id` / `related_player_id` | integer      | Player(s) involved, null for team-level entries like corners                                                                                                                                         |
| `addition`                        | string       | Human-readable ordinal label (e.g. "1st Corner", "3rd Shot On Target")                                                                                                                               |
| `minute` / `extra_minute`         | integer      | When the entry occurred                                                                                                                                                                              |
| `rescinded`                       | boolean/null | Whether this entry was later corrected or removed, see the [Events corrections callout](https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/events) for how this is used on goals |
| `sort_order`                      | integer      | Order within its type/period grouping                                                                                                                                                                |

### weatherReport

#### What it returns

`include=weatherReport` returns current weather conditions at the venue. Note the requested include is camelCase (`weatherReport`), but **the key in the response body comes back lowercase** as `weatherreport`, build your parsing with this in mind.

{% hint style="warning" %}
**Attendance is not part of this object.** If you need attendance figures, they live elsewhere on the fixture response, not inside `weatherreport`.
{% endhint %}

#### Example response

```json
{
  "weatherreport": {
    "id": 772335,
    "fixture_id": 19714695,
    "venue_id": 332,
    "temperature": {
      "current": 30.24
    },
    "feels_like": {
      "current": 29.42
    },
    "wind": {
      "speed": 0.89,
      "direction": 200
    },
    "humidity": "35%",
    "pressure": 1013,
    "clouds": "69%",
    "description": "broken clouds",
    "icon": "https://cdn.sportmonks.com/images/weather/04d.png",
    "type": "actual",
    "metric": "celcius",
    "current": {
      "temp": 30.24,
      "wind": 0.89,
      "clouds": "69%",
      "humidity": "35%",
      "pressure": 1013,
      "direction": 200,
      "feels_like": 29.42,
      "description": "broken clouds"
    }
  }
}
```

#### Field descriptions

| Field                           | Type            | Description                                             |
| ------------------------------- | --------------- | ------------------------------------------------------- |
| `id`                            | integer         | Unique identifier for this weather report               |
| `fixture_id`                    | integer         | The fixture this report belongs to                      |
| `venue_id`                      | integer         | The venue where conditions were recorded                |
| `temperature.current`           | float           | Temperature at time of recording                        |
| `feels_like.current`            | float           | Perceived temperature                                   |
| `wind.speed` / `wind.direction` | float / integer | Wind speed and direction in degrees                     |
| `humidity`                      | string          | Relative humidity as a percentage string                |
| `pressure`                      | integer         | Atmospheric pressure                                    |
| `clouds`                        | string          | Cloud cover as a percentage string                      |
| `description`                   | string          | Human-readable summary (e.g. "broken clouds")           |
| `icon`                          | string          | URL to a weather icon                                   |
| `type`                          | string          | e.g. `"actual"`                                         |
| `metric`                        | string          | Unit system, e.g. `"celcius"`                           |
| `current`                       | object          | Flattened duplicate of the fields above for convenience |

***

### periods.statistics

#### What it returns

`include=periods.statistics` works and returns each period (1st half, 2nd half, extra time, etc.) with a nested `statistics` array scoped to that period only. This lets you break down stats like possession or shots by half, rather than only getting fixture-wide totals.

#### Example response (abbreviated)

```json
{
  "periods": [
    {
      "id": 7032992,
      "fixture_id": 19714695,
      "type_id": 1,
      "started": 1786270567,
      "ended": 1786273439,
      "sort_order": 1,
      "description": "1st-half",
      "period_length": 45,
      "statistics": [
        {
          "id": 301604523,
          "fixture_statistics_id": 956129228,
          "fixture_id": 19714695,
          "type_id": 80,
          "period_id": 7032992,
          "participant_id": 73,
          "data": {
            "value": 298
          }
        }
      ]
    }
  ]
}
```

#### Field descriptions

<table data-search="false"><thead><tr><th>Field</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td><code>id</code></td><td>integer</td><td>Unique identifier for this period</td></tr><tr><td><code>type_id</code></td><td>integer</td><td><code>1</code> = 1st half, <code>2</code> = 2nd half, others exist for extra time/penalties, see the <a href="https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/periods">States and Periods tutorial</a></td></tr><tr><td><code>description</code></td><td>string</td><td>Human-readable period name</td></tr><tr><td><code>statistics</code></td><td>array</td><td>Same shape as the top-level <code>statistics</code> include, but scoped to this period only</td></tr><tr><td><code>statistics[].type_id</code></td><td>integer</td><td>The statistic type, decode via <a href="https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/statistics/fixture-statistics"><code>statistics.type</code></a></td></tr><tr><td><code>statistics[].participant_id</code></td><td>integer</td><td>Which team this stat belongs to</td></tr><tr><td><code>statistics[].data.value</code></td><td>number</td><td>The stat value</td></tr></tbody></table>

To combine with the type names, add the nested include: `include=periods.statistics.type`.

### A note on `rule` / `rule.type`

**`rule` is not a valid include on the Fixture entity.** Requesting `include=rule.type` on a fixture returns a 404 with error code 5013 ("The requested include 'rule' does not exist on Fixture"). If you're looking to determine promotion, relegation, or qualification logic for a knockout stage, check the **Standings** entity instead, that's where this kind of rule data is expected to live. This page will be updated once that's confirmed.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sportmonks.com/v3/tutorials-and-guides/tutorials/includes/fixture-includes-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.