# 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: 29th 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:
**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:**
* \
* \
**b) Element attributes:**
Attributes of \ element:
* sport\_event\_id = id of the event
* update\_time
---
# 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.sportradar.com/uof/support-and-history/archived/deprecated-uof-endpoints/fixture_change-end-point.md?ask=
```
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.