# GET Expected by Team

{% tabs %}
{% tab title="Base URL" %}

```
https://api.sportmonks.com/v3/football/expected/fixtures
```

{% endtab %}

{% tab title="Example Response" %}

```
{
  "data": [
    {
      "id": 26898369,
      "fixture_id": 18898173,
      "type_id": 5304,
      "participant_id": 10010,
      "data": {
        "value": 1.0674
      },
      "location": "home"
    },
    {
      "id": 26898370,
      "fixture_id": 18898173,
      "type_id": 5304,
      "participant_id": 7011,
      "data": {
        "value": 1.8234
      },
      "location": "away"
    },
```

{% endtab %}

{% tab title="Field Description" %}

| Field           | Description                                              | Type    |
| --------------- | -------------------------------------------------------- | ------- |
| id              | Refers to the unique id of the expected value.           | integer |
| fixture\_id     | Refers to the fixture related to the value.              | integer |
| type\_id        | Refers to the type of the Expected value.                | integer |
| participant\_id | Refers to the participant related to the Expected value. | integer |
| value           | Displays the value.                                      | integer |
| location        | Refers to the location of the home or away team.         | string  |
| {% endtab %}    |                                                          |         |
| {% endtabs %}   |                                                          |         |

{% tabs %}
{% tab title="Query Parameters" %}

<table><thead><tr><th>Query Parameters</th><th width="164.33333333333331">Required?</th><th>Description</th></tr></thead><tbody><tr><td><code>api_token</code></td><td>YES</td><td>Your unique API token</td></tr><tr><td><code>include</code></td><td>NO</td><td>Enrich the API with more data by using includes</td></tr><tr><td><code>select</code></td><td>NO</td><td>Select specific fields on the base entity.</td></tr><tr><td><code>filters</code></td><td>NO</td><td><p>Filter the API response on multiple related entities. There are static filters and dynamic filters.</p><p></p><p>Please find the possibilities in the Static and Dynamic Filter tab.</p></td></tr></tbody></table>
{% endtab %}

{% tab title="Static Filters" %}
Not applicable for this endpoint.
{% endtab %}

{% tab title="Dynamic Filters" %}
The **dynamic filters** are based on entities and includes. Each dynamic filter uses an entity to filter on and one entity to apply the filter to. Below is an example with an explanation of how filters are set up. For more information, please look at our[ Filters page](https://docs.sportmonks.com/football/api/request-options/filtering).

{% hint style="info" %}
Using an include? Check their respective filters on their entity page. For example if you use `&include=fixtures`, you can apply [fixture-related filters](https://docs.sportmonks.com/football/endpoints-and-entities/entities/fixture#fixture-entity-filters).
{% endhint %}

| Dynamic Filters | Available on entity | Description                                                            | Examples                                                                                                                                                     |
| --------------- | ------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `types`         | Statistics          | Filter the statistics on a selection of type IDs separated by a comma. | <p><code>\&include=statistics\&filters=fixtureStatisticTypes:TYPEIDS</code></p><p><code>\&include=statistics\&filters=fixtureStatisticTypes:42,49</code></p> |
| {% endtab %}    |                     |                                                                        |                                                                                                                                                              |
| {% endtabs %}   |                     |                                                                        |                                                                                                                                                              |

{% hint style="info" %}
Please note that the availability of xG values varies depending on the package you choose.&#x20;

* The **Basic** package offers access straight after the match has finished to all xG statistics.
* The **Advanced** package offers real-time availability to all xG statistics.

You can find more information on our dedicated [pricing page](https://www.sportmonks.com/football-api/plans-pricing).&#x20;
{% endhint %}

#### Pagination

Yes

#### Include depth

You can use a total of `3` nested includes on this endpoint

#### Include options

[`type`](/v3/endpoints-and-entities/endpoints/types.md) [`fixture`](/v3/endpoints-and-entities/entities/fixture.md) [`participant`](/v3/endpoints-and-entities/endpoints/teams.md)

**Related Entities:**

Get an overview and explanation of all the fields returned in the API response. The related entities for the expected endpoints are:

* [Expected](/v3/endpoints-and-entities/entities/expected.md)

[![Run in Postman](https://run.pstmn.io/button.svg)](https://app.getpostman.com/run-collection/11949411-c7a3a0a0-b5c5-4109-9bf6-f430fec65316?action=collection%2Ffork\&collection-url=entityId%3D11949411-c7a3a0a0-b5c5-4109-9bf6-f430fec65316%26entityType%3Dcollection%26workspaceId%3D17c720d0-d97b-42a9-9ea7-23260ed53ddf)


---

# Agent Instructions: 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:

```
GET https://docs.sportmonks.com/v3/endpoints-and-entities/endpoints/expected-xg/get-expected-by-team.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.