Ctrlk
sportradar.comSportradar Support Portal
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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<sport_event_status> 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 <result> elements (key value pairs):

<sport_event_status status="ended" period_of_leader="52">
    <results>
        <competitor id="sr:competitor:{id}">
            <result value="4" type="position"/>
            <result value="52" type="finished_laps"/>
            <result value="1" type="no_pitstops"/>
            <result value="2" type="no_overtakings"/>
            <result value="01:29.482" type="fastest_lap"/>
            <result value="+00:19.650" type="time"/>
        </competitor>
...
        <competitor id="sr:competitor:{id}">
            <result value="20" type="position"/>
            <result value="0" type="no_pitstops"/>
            <result value="0" type="no_overtakings"/>
            <result value="1" type="retired_in_lap"/>
        </competitor>
    </results>
</sport_event_status>

Additional attributes within the summary endpoint explained: <sport_event_status>

  • period_of_leader Reflecting the current lap of the leader in the race.

  • status Possible values: not_started, live, ended, unknown.

API call:

Example Response

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).

Additional attributes within the period_summary endpoint explained: <period_status>

  • 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:

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.

Example response for all drivers and for selectively lap 2:

PreviousFormula 1 UOF API fixture informationNextFormula 1 via Replay Server

Last updated

Was this helpful?