> 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/live-competition-odds/live-odds-nascar/nascar-uof-api-fixture-information.md).
# Nascar UOF API fixture information
### **UOF API - Sport & Category**
```xml
```
### **UOF API - Nascar fixtures & their stages**
{% code lineNumbers="true" %}
```xml
Response headers
accept-ranges: bytes
access-control-allow-origin: *
access-control-expose-headers: server,date,content-type,transfer-encoding,connection,cache-control,x-envoy-upstream-service-time,content-encoding,x-srv,x-sbe,vary,x-varnish,age,via,accept-ranges,x-final-url,access-control-allow-origin
```
{% endcode %}
{% hint style="info" %}
**Please note**
* Various event stages belong to a season stage and the event schedule of a specific season can be fetched from the UOF API schedule endpoints.
* The sport and the category where a specific stage is connected to are specified within the \ and \ elements.
{% endhint %}
**Event stage (in Nascar the race is happening under this stage)**
{% code title="Event Stage (for the Ally 400 in Nashvile in 2022)" lineNumbers="true" %}
```xml
```
{% endcode %}
**Parents of the event stage are reflected in \ and have the stage\_type "season".**
{% hint style="danger" %}
No Race Stage
It is important to highlight that there is no race stage under the event stage for Nascar. This means the races take place on the event stage itself. This is different to all motorsports offered so far!
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sportradar.com/uof/live-competition-odds/live-odds-nascar/nascar-uof-api-fixture-information.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.