> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/api-and-structure/api/static-sport-event-information/fixture-changes-endpoint.md).
# Fixture Changes Endpoint
XML example
```
```
**Endpoint Parameters**
You can customize the endpoint response by using the following parameters.
| Parameter | Description | Possible Values |
| ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| language
Required
| Language code for translation. | See all supported languages and their codes on [language support](/uof/introduction/language-support.md) |
| afterDateTime
Optional
| 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). | ISODate format (YYYY-MM-DDThh:mm:ss).
E.g: 2023-05-29T12:05:00
|
| sportId
Optional
| The id of the sport you want the fixture changes for. | Format - sr:sport:{id}
E.g: sr:sport:1
|
### Endpoint Structure
The main elements and sub-elements provided by the Fixture endpoints are the ones shown in the list below:
* \
* \
### Attributes Explained
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 |
###
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.sportradar.com/uof/api-and-structure/api/static-sport-event-information/fixture-changes-endpoint.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.