Matches List

When requesting a list of upcoming matches, POST request is:

Required fields for this call are the tournament_id and number of days in future

With the above details the API provides the following message:

<tournament_fixtures timestamp="1613747295271">
  <tournament id="18" name="Championship"/>
  <fixtures_fixture>
    <fixture id="match:23217017" start_time="2021-02-19T19:45:00+0000">
      <sport id="1" name="Soccer"/>
      <category id="1" name="England"/>
        <competitors>
          <competitor id="24" name="Watford FC"/>
          <competitor id="27" name="Derby County"/>
        </competitors>
    </fixture>
    <fixture id="match:23216999" start_time="2021-02-20T12:30:00+0000">
      <sport id="1" name="Soccer"/>
      <category id="1" name="England"/>
        <competitors>
          <competitor id="11" name="Coventry City"/>
          <competitor id="50" name="Brentford FC"/>
        </competitors>
    </fixture>
    <fixture id="match:23216995" start_time="2021-02-20T15:00:00+0000">
      <sport id="1" name="Soccer"/>
      <category id="1" name="England"/>
        <competitors>
           <competitor id="58" name="Bristol City"/>
           <competitor id="23" name="Barnsley"/>
        </competitors>
     </fixture>
  </fixtures_fixture>
</tournament_fixtures>

Tag tournament_fixtures has only one attribute which is timestamp with date and time when message was created.

Under that tag there are tags named tournament and fixtures_fixture. Tag named tournament has ID of tournament and its name. Tag fixtures_fixture contains tags fixture.

Tag fixture contains all relevant information of a match, attributes match id and start time for that match..

Inside it are tags sport which have ID and name for sport, and 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