Retrieving results

This page describes the way of requesting results, during a live session or after it.

Endpoints and includes for retrieving results

Results are retrievable via includes available on all Live and Fixtures endpoints, however they can also be retrieved via most endpoints where you can include fixtures. For example on the GET Fixture by ID endpoint:

https://api.sportmonks.com/v3/motorsport/fixtures/19408487
?api_token=YOUR_TOKEN
&include=results

Or, if you want to get the results for the whole season, you can use a nested include:

https://api.sportmonks.com/v3/motorsport/seasons/25273
?api_token=YOUR_TOKEN
&include=fixtures.results

The response will show the results under the fixture:

These types are available in the result include:

Developer name (description)
Explanation

TIME

  • The latest lap time (races)

  • The fastest lap time (practices and qualifications)

INTERVAL

  • Interval between this driver and the driver ahead (if the driver is not leading; no + prefix)

  • The amount of laps behind (if the driver is not leading, e.g. '1 lap'; no + prefix)

  • The total racing time, if available (If the driver is P1)

GAP_TO_LEADER

  • The time gap between this driver and the leading driver (if the driver is not leading, no + prefix)

  • The amount of laps behind (if the driver is not leading, e.g. '1 lap', no + prefix)

  • The total racing time, if available (if the driver is P1)

  • DNS/DNF status (Note: We recommend to use the dedicated STATUS type instead - this is available in the lineup details, described further on this page)

POSITION

The current position of the driver in the race

TYRE

The current used tyre comound (SOFT, MEDIUM, HARD, INTERMEDIATE, WET, TEST_UNKNOWN*) and age since start (in number of laps) *TEST_UNKNOWN is a type only used during pre-season testing sessions, and means that a driver is testing prototype tyres

Matching results to the driver

To match each result to a driver, you have three options:

  1. Pre-load all the drivers into your application using the GET All Drivers endpoint (Recommended for an initial data load)

  2. Use the lineups.driver nested include to retrieve all the drivers for the fixture (Recommended at least at the session start, to retrieve any new drivers)

  3. Including the driver on the result using the results.participant nested include (Not recommended due to decreased performance and larger responses)

The 'lineup details' alternative

The results include gives you a subset of the most important result data. Do you need more?You can use the lineups.details include to retrieve the full set of types using this endpoint:

In the table below is an explanation of all the types available using this include:

Developer name
Explanation

TIME

  • The latest lap time (races)

  • The fastest lap time (practices and qualifications)

INTERVAL

  • Interval between this driver and the driver ahead (if the driver is not leading; no + prefix)

  • The amount of laps behind (if the driver is not leading, e.g. '1 lap'; no + prefix)

  • The total racing time, if available (If the driver is P1)

GAP_TO_LEADER

  • The time gap between this driver and the leading driver (if the driver is not leading, no + prefix)

  • The amount of laps behind (if the driver is not leading, e.g. '1 lap', no + prefix)

  • The total racing time, if available (if the driver is P1)

  • DNS/DNF status (Note: We recommend to use the dedicated STATUS type instead - see STATUS below)

POSITION

The current position of the driver in the race

STATUS

The status of the driver: DNS/DNF/DSQ

TYRE

The current used tyre comound (SOFT, MEDIUM, HARD, INTERMEDIATE, WET, TEST_UNKNOWN*) and age since start (in number of laps) *TEST_UNKNOWN is a type only used during pre-season testing sessions, and means that a driver is testing prototype tyres

LAPS

The amount of laps

PITSTOPS

The amount of pitstops

FASTEST_LAP

The driver fastest lap time and the lap number

POINTS

The points that would be assigned to the driver if they finish on their current position (live) or the points received for the race (after race), only available for race type sessions

GRID_POSITION

The grid position, only available for race type sessions

This include is a bit more advanced, as the type is not included by default. However, with the lineups include, the driver name, number and grid position is also included in the response. In the example below, the include is enriched with types by using lineups.details.type:

Last updated

Was this helpful?