search
Quick StartFootball APIContactAPI 3.0

Nested includes

We ended the previous chapter with a small teaser about nested includes. Now in this part, we finally present to you the nested include. This tutorial will teach you what it is, where it is used and how you can apply them yourself.

hashtag
Nested includes and relationships

Life is all about relationships. You are, for example, your parents’ child, your sister’s sibling, etc. Nested includes are no different from this because they too share a relationship with includes. The nested include allows you to further enrich your data, by requesting more information from a standard include. Might sound difficult, but we assure you, it’s anything but hard. This is how we use Nested includes.

hashtag
Create your request

For example, in our includes tutorial you’ve enriched your fixture by datearrow-up-right request with the team and events includes:

https://soccer.sportmonks.com/api/v2.0/fixtures/date/2020-08-02?api_token={API_TOKEN}&include=localTeam,visitorTeam,events

The include event shows you the data about players who received a card, scored a goal, or were substituted. A snippet of the response:

            "events": {
                "data": [
                    {
                        "id": 16475287001,
                        "team_id": "338",
                        "type": "yellowcard",
                        "var_result": null,
                        "fixture_id": 16475287,
                        "player_id": 174161,
                        "player_name": "S. Martin",
                        "related_player_id": null,
                        "related_player_name": null,
                        "minute": 17,
                        "extra_minute": null,
                        "reason": null,
                        "injuried": null,
                        "result": null
                    },
                    {
                        "id": 16475287002,
                        "team_id": "53",
                        "type": "goal",
                        "var_result": null,
                        "fixture_id": 16475287,
                        "player_id": 96792,
                        "player_name": "O. Édouard",
                        "related_player_id": 173080,
                        "related_player_name": "G. Taylor",
                        "minute": 20,
                        "extra_minute": null,
                        "reason": null,
                        "injuried": null,
                        "result": "1-0"
                    },
                    {
                        "id": 16475287003,
                        "team_id": "53",
                        "type": "goal",
                        "var_result": null,
                        "fixture_id": 16475287,
                        "player_id": 8403182,
                        "player_name": "J. Frimpong",
                        "related_player_id": 173080,
                        "related_player_name": "G. Taylor",
                        "minute": 31,
                        "extra_minute": null,
                        "reason": null,
                        "injuried": null,
                        "result": "2-0"
                    },
                    {
                        "id": 16475287004,
                        "team_id": "338",
                        "type": "own-goal",
                        "var_result": null,
                        "fixture_id": 16475287,
                        "player_id": 32761,
                        "player_name": "C. Jullien",
                        "related_player_id": null,
                        "related_player_name": null,
                        "minute": 34,
                        "extra_minute": null,
                        "reason": null,
                        "injuried": null,
                        "result": "2-1"
                    },
                    
            }

But, what if we want to know more about these players, who scored a goal, like their country of origin, height, weight, age, image, etc. This is where the nested include comes into play!

hashtag
Using nested includes

Because the include event is related to a player. You can add .playerto the include, which will result in the nested include: events.player

The nested includes are represented in the form of dots (.), which are then linked to a standard include. This shows their relationship.

Now you've learnt how to enrich your response. In the next chapter you will learn how you can filter, sort and limit the response.

PreviousIncludesNextFiltering, limiting & sorting

Last updated

Was this helpful?