# Fixture\_change end point

The Fixture Changes End Point provides the customer with the list of all the fixture changes from a certain date till now.

Filters are available in order to customize the answer of the call according to date and sport.

**Filters:**

* Date: API End point will return all the fixture changes from such a date onwards (till the timing of the call).
* Sport: API will return the fixture changes related to the sport whose ID is inserted

**Filter format:**

* Sport: the ID of the sport for which fixture changes are requested will be inserted in the Sport Textbox  with the following format sr:sport: \[Sport Integer ID]
* Date: the date since when fixture changes are requested will be inserted in the Date Textbox. The format of the date to insert will be the following: AAAA-MM-DDThh:mm:ss. 
  * Example: 29<sup>th</sup> May 1977 12:05:00 will be 1977-05-29T12:05:00
  * The date inserted must be within the last 24 hours

Filters in Fixture Changes API End Point  are shown in Figure below:

![](https://1868790214-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1KlIQPveu0EGYCTI8DL1%2Fuploads%2FWLdOaBD4n6Bz3DRs9rRy%2F25657423.png?alt=media)

&#x20;**Fixture Changes API End point content:**

The End Point will return a list of xml elements with the following information:

* Id of the Sport Event
* Time of the change

Once the customer is aware that a fixture change happened, Timeline and Summary API End Points can be used in order to retrieve detailed information about the change.

**Fixture changes API End Point element and attributes:**

**a)        Elements in Fixture Changes end point:**

* \<Fixture\_changes>
* \<Fixture\_change>

**b)        Element attributes:**&#x20;

Attributes of \<Fixture\_change> element:

* sport\_event\_id = id of the event
* update\_time