Match Fixture
- Karl
When requesting a Match fixture, POST request is:
Required field for this call is the match_id
With the above details the API provides the following message:
<fixtures_fixture timestamp="1648816365659">
<fixture id="match:27751662" start_time="2022-04-02T13:30:00+02:00">
<sport id="1" name="Soccer"/>
<category id="1" name="England"/>
<tournament id="17" name="Premier League"/>
<competitors>
<competitor id="competitor:44" name="Liverpool FC">
<translations>
<translation lang="de" name="Liverpool FC"/>
<translation lang="en" name="Liverpool FC"/>
<translation lang="es" name="Liverpool FC"/>
<translation lang="fr" name="Liverpool FC"/>
<translation lang="it" name="Liverpool"/>
<translation lang="pt" name="Liverpool FC"/>
</translations>
</competitor>
<competitor id="competitor:24" name="Watford FC">
<translations>
<translation lang="de" name="Watford FC"/>
<translation lang="en" name="Watford FC"/>
<translation lang="es" name="Watford FC"/>
<translation lang="fr" name="Watford FC"/>
<translation lang="it" name="Watford"/>
<translation lang="pt" name="Watford FC"/>
</translations>
</competitor>
</competitors>
</fixture>
</fixtures_fixture>Tag fixtures_fixture has only one attribute which is timestamp with date and time when fixture message was created.
Under the tag fixtures_fixture there is a tag named fixture that has id of match and start_time for that match. That tag contains all relevant information of a match, inside it are tags sport, category and tournament which have ID and name for sport, category and tournament of the requested match.
After, there is competitors tag which contains data for both competitors placed into child competitor tags. Tags competitor have attribute representing ID of competitor and name attribute that represents name of the competitor. If translations are included we will have child tags translation under the tag translations that will contain attributes lang which indicates the ISO language code and name for competitor name in that specified language.