# \ #### What is sport\_event element? The *sport\_event* element provides information related to a match/fixture. This element identifies the match in a very similar way to the fixture element described in [Fixture endpoint](/uof/api-and-structure/api/static-sport-event-information/fixture-endpoint.md). #### Structure / Sub-elements {% hint style="success" %} Change hint typeFor a full breakdown of each endpoint and its structure, refer to the [Element page](https://app.gitbook.com/o/ZO6TPSCtikUxdBddrKNy/s/1KlIQPveu0EGYCTI8DL1/~/changes/156/api-and-structure/api/elements) {% endhint %} * \ * * \ * \ * \ * \ * \ * \ * \ * \ #### Example XML Response Snippet ```xml ``` #### Element Attributes The table below shows the attributes of the sport\_event element. | Attribute | Meaning | Possible values | | ------------------ | -------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *id* | Unique identifier of the event |

Numeric string

Example: id="sr:match:43901686"

| | *scheduled* | Specifies when the specific match will start |

Datetime

Example: scheduled="2024-03-02T11:00:00+00:00"

| | *start\_time\_tbd* | Specifies if the starting time is confirmed or not |

TRUE
FALSE

| | *liveodds* | Explains the situation of the liveodds for the match, if the match can be bought, booked or if it is not available at all. |

BOOKABLE The match can be booked
BOOKED The match is booked
BUYABLE The match is bookable, if the client buys the proper package
NOT\_AVAILABLE Either the match does not exist, or the match is not visible by the client

| | *next\_live\_time* | specifies when the event is live, the next time |

Datetime

Example: next\_live\_time="2024-03-03T16:00:00+00:00"

| ``` ``` --- # 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/elements/less-than-sport_event-greater-than.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.