# Formula 1 UOF API score information
In-running statistics for Formula 1 races are provided via the summary endpoint in the Unified Odds API.
The\ element inlcludes the attribute **period\_of\_leader** indicating the current lap of the leading driver.
\
For each driver the following statistics are available:
* **position**\
Reflecting the position of a driver (Integer).
* **time**\
(Optional) Reflecting the time-difference to the leader in the format +mm:ss.SSS (String)**.**\
Please note:\
For the leader the value reflects his entire race time in the format HH:mm:ss.SSS**.**\
If a driver retires, this attribute won't be exposed anymore, but the retired\_in\_lap attribute will be added instead.
* **finished\_laps**\
(Optional) Reflecting the number of laps which a specific driver has finished (Integer).
* **fastest\_lap**\
Reflecting the fastest lap of a specific driver in the format mm:ss.SSS (String).
* **no\_pitstops**\
Reflecting the number of pitstops made by a specific driver (Integer).
* **no\_overtakings**\
Reflecting the number of overtakings by a driver according to our sports betting rules (Integer).
* **retired\_in\_lap**\
(Optional) Reflecting the lap in which a specific driver has retired (Integer).
\
The mentioned statistics are exposed for all competitors within multiple \ elements (key value pairs):
```xml
...
```
Additional attributes within the summary endpoint explained:\
\
\&#xNAN;**\**
* **period\_of\_leader** \
Reflecting the current lap of the leader in the race.
* **status** \
Possible values: not\_started, live, ended, unknown.
\
API call:
```xml
api.betradar.com/v1/sports/en/sport_events/sr:stage:{id}/summary.xml
```
Example Response
```xml
```
An additional API endpoint (period\_summary.xml) is available to fetch lap statistics such as:
* **time**\
(Optional) Reflecting the lap time of a specific driver (String)\
If a driver retired, this attribute won't be exposed anymore, but the retired\_in\_lap attribute will be added instead.\
Please note:\
The lap time is updated after the lap is finished.
* **pitstop** \
(Optional) Indicating if a driver was taking a pitstop in the specific lap (boolean).\
If a driver retired, this attribute won't be exposed anymore, but the retired\_in\_lap attribute will be added instead.\
Please note:\
The lap where the driver enters the pit is considered valid.
* **no\_overtakings**\
(Optional) Reflecting the number of overtakings by a driver within the specified lap according to our sports betting rules (Integer).\
If a driver retired, this attribute won't be exposed anymore, but the retired\_in\_lap attribute will be added instead.
* **retired\_in\_lap**\
(Optional) Reflecting the lap in which a specific driver has retired (Integer).
```xml
...
...
```
Additional attributes within the period\_summary endpoint explained:\
\
\&#xNAN;**\**
* **type** \
Possible values: lap
* **status** \
Possible values: not\_started, started, completed.
* **number**\
Indicating the number of the specific lap.
\
API call and related query parameters:
```json
api.betradar.com/v1/sports/en/sport_events/sr:stage:{id}/period_summary.xml?competitors=sr:competitor:{id}&competitors=sr:competitor:{id}&periods=2&periods=3&periods=4
```
{% hint style="info" %}
**Note**
As query parameters you can insert multiple competitors & multiple periods reflecting the laps . If you don't provide a query parameter, the response will include all competitors and all laps of a race.
{% endhint %}
Example response for all drivers and for selectively lap 2:
```xml
```
---
# 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/live-competition-odds/live-odds-formula-1/formula-1-uof-api-score-information.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.