# Fixture Changes Endpoint

XML example

```
<fixture>
<scheduled_start_time_changes>
<scheduled_start_time_change old_time="2018-03-23T11:00:00+00:00" new_time="2018-09-07T10:00:00+00:00" changed_at="2018-03-14T00:07:23+00:00"/>
</scheduled_start_time_changes>
</fixture>
```

**Endpoint Parameters**

You can customize the endpoint response by using the following parameters.

| Parameter                                                        | Description                                                                                                                                                 | Possible Values                                                                                          |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| <p><em>language</em></p><p><strong>Required</strong></p>         | Language code for translation.                                                                                                                              | See all supported languages and their codes on [language support](/uof/introduction/language-support.md) |
| <p><em>afterDateTime</em></p><p><strong>Optional</strong></p>    | the datetime after which you want the fixture changes. The endpoint returns all the fixture changes from such a date onwards (till the timing of the call). | <p>ISODate format (YYYY-MM-DDThh:mm:ss).</p><p>E.g: 2023-05-29T12:05:00</p>                              |
| <p><em>sportId</em></p><p><em><strong>Optional</strong></em></p> | The id of the sport you want the fixture changes for.                                                                                                       | <p>Format - sr:sport:{id}</p><p>E.g: sr:sport:1</p>                                                      |

### Endpoint Structure <a href="#uofapifixturechangesendpoint-endpointstructure" id="uofapifixturechangesendpoint-endpointstructure"></a>

The main elements and sub-elements provided by the Fixture endpoints are the ones shown in the list below:

* \<fixture\_changes>
  * \<fixture\_change>

### Attributes Explained <a href="#uofapifixturechangesendpoint-attributesexplained" id="uofapifixturechangesendpoint-attributesexplained"></a>

The following attributes are found in the *fixture change element*.

| Name               | Description                                           |
| ------------------ | ----------------------------------------------------- |
| *sport\_event\_id* | the unique id assigned to the sport event by SR       |
| *update\_time*     | the date and time when the fixture is updated/changed |

### &#x20;<a href="#uofapifixturechangesendpoint-xmlexample" id="uofapifixturechangesendpoint-xmlexample"></a>

<br>


---

# 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/api-and-structure/api/static-sport-event-information/fixture-changes-endpoint.md?ask=<question>
```

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.