Indy Lights v2

Frequently Asked Questions
Quick Access
Postman Collection XSD Schema
Download
## Indy Lights API Overview The Indy Lights API provides schedules and post-race results for the entire Indy Lights series. All data is collected via Sportradar’s expert operators. Select the Indy Lights package in our Coverage Matrix for events and data offered. This API uses a descending, stage-based structure. By changing the stage ID, you can retrieve information on a season, event, race, or any of the practice or qualifying stages. Additional feeds provide complimentary stats, including racer profiles.
API API Version
Indy Lights v2
Note: Authentication is required for all API calls.
## Indy Lights v2 API Map To best utilize the Indy Lights API, you will need several parameters to create your API calls. The map below illustrates how you can obtain the parameters you need. >

Example:

>To find the profile for a given racer: >
  1. Call the Seasons endpoint and find the Stage Id for the current season
  2. Call the Stage Schedule using the 'season' Stage Id
  3. Locate the Stage Id which your race competed in
  4. Call the Stage Summary using the 'race' Stage Id
  5. Within the results locate the competitor id for your racer
  6. Call the Competitor Profile endpoint using your racer's competitor id
The primary Seasons feed requires only a human-readable parameter to call the endpoint. This feed provides season Stage Ids, which can be used to generate descending Stage Summary feeds to include more detailed info, such as events and races. These feeds can then be used to generate the profile feed. ## Competitor Merge Mappings Provides the valid Sportradar Id in cases when two competitors have been merged into one. Mapping entries will remain in the feed for 7 days.
Update Frequency: As Necessary
Content Type: XML or JSON
Mappings Info Data Points: Name Merged Id Retained Id
```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.com/indylights/trial/v2/en/competitors/merge_mappings.xml?api_key={your_api_key}") http = Net::HTTP.new(url.host, url.port) http.use_ssl = true http.verify_mode = OpenSSL::SSL::VERIFY_NONE request = Net::HTTP::Get.new(url) response = http.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.sportradar.com") conn.request("GET", "/indylights/trial/v2/en/competitors/merge_mappings.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.com/indylights/trial/v2/en/competitors/merge_mappings.xml?api_key={your_api_key}" ``` > The above command returns xml structured like this. Access the Competitor Merge Mappings feed by replacing the parameters in the following URL: https://api.sportradar.com/indylights/`{access_level}`/`{version}`/`{language_code}`/competitors/merge_mappings.`{format}`?api_key=`{your_api_key}` | Parameter | Description | | --------- | ----------- | | `access_level` | Defines the access level of your API key as Production (production) or Trial (trial). | | `version` | Version number of the API you are accessing (Current Version: v2). | | `language_code` | Supported Locales | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Competitor Profile Provides biographical information for a given driver.
Update Frequency: As Necessary
Content Type: Raw XML or JSON
Competitor Information Data Points: Gender Id Name
```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.com/indylights/trial/v2/en/competitors/sr:competitor:687815/profile.xml?api_key={your_api_key}") http = Net::HTTP.new(url.host, url.port) http.use_ssl = true http.verify_mode = OpenSSL::SSL::VERIFY_NONE request = Net::HTTP::Get.new(url) response = http.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.sportradar.com") conn.request("GET", "/indylights/trial/v2/en/competitors/sr:competitor:687815/profile.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.com/indylights/trial/v2/en/competitors/sr:competitor:687815/profile.xml?api_key={your_api_key}" ``` > The above command returns xml structured like this. Access the Competitor Profile feed by replacing the parameters in the following URL: https://api.sportradar.com/indylights/`{access_level}`/`{version}`/`{language_code}`/competitors/`{competitor_id}`/profile.`{format}`?api_key=`{your_api_key}` | Parameter | Description | | --------- | ----------- | | `access_level` | Defines the access level of your API key as Production (production) or Trial (trial). | | `version` | Version number of the API you are accessing (Current Version: v2). | | `language_code` | 2 letter code for supported languages: en (English). | | `competitor_id` | Id of a given competitor. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Deleted Stages Provides all deleted stages within a given season.
Update Frequency: As Necessary
Content Type: Raw XML or JSON
Stage Information Data Points: Description
Disabled
Scheduled
Scheduled End
Stage Id
Status
Type
```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.com/indylights/trial/v2/en/seasons/sr:stage:985207/deleted_stages.xml?api_key={your_api_key}") http = Net::HTTP.new(url.host, url.port) http.use_ssl = true http.verify_mode = OpenSSL::SSL::VERIFY_NONE request = Net::HTTP::Get.new(url) response = http.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.sportradar.com") conn.request("GET", "/indylights/trial/v2/en/seasons/sr:stage:985207/deleted_stages.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.com/indylights/trial/v2/en/seasons/sr:stage:985207/deleted_stages.xml?api_key={your_api_key}" ``` Access the Deleted Stages feed by replacing the parameters in the following URL: https://api.sportradar.com/indylights/`{access_level}`/`{version}`/`{language_code}`/seasons/`{stage_id}`/deleted_stages.`{format}`?api_key=`{your_api_key}` | Parameter | Description | | --------- | ----------- | | `access_level` | Defines the access level of your API key as Production (production) or Trial (trial). | | `version` | Version number of the API you are accessing (Current Version: v2). | | `language_code` | 2 letter code for supported languages: en (English). | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Seasons Provides a complete historical list of available seasons. This is the starting point for the Indy Lights API.
Update Frequency: As Necessary
Content Type: Raw XML or JSON
Category & Sport Information Data Points: Category Id
Category Name
Sport Id Sport Name
Stage Information Data Points: Description
Disabled
Scheduled
Scheduled End
Single Event
Stage Id
Type
```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.com/indylights/trial/v2/en/seasons.xml?api_key={your_api_key}") http = Net::HTTP.new(url.host, url.port) http.use_ssl = true http.verify_mode = OpenSSL::SSL::VERIFY_NONE request = Net::HTTP::Get.new(url) response = http.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.sportradar.com") conn.request("GET", "/indylights/trial/v2/en/seasons.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.com/indylights/trial/v2/en/seasons.xml?api_key={your_api_key}" ``` > The above command returns xml structured like this. Access the Seasons feed by replacing the parameters in the following URL: https://api.sportradar.com/indylights/`{access_level}`/`{version}`/`{language_code}`/seasons.`{format}`?api_key=`{your_api_key}` | Parameter | Description | | --------- | ----------- | | `access_level` | Defines the access level of your API key as Production (production) or Trial (trial). | | `version` | Version number of the API you are accessing (Current Version: v2). | | `language_code` | 2 letter code for supported languages: en (English). | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Stage Schedule Provides the schedule for a given stage.
Update Frequency: As Necessary
Content Type: Raw XML or JSON
Category & Sport Information Data Points: Category Id
Category Name
Sport Id Sport Name
Stage Information Data Points: Circuit
Description
Disabled
Scheduled
Scheduled End
Single Event
Stage Id
Status
Type
Venue Information Data Points: City
Coordinates
Country
Country Code
Curves Left
Curves Right
Debut
Id
Length
Name
Official URL
Timezone
```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.com/indylights/trial/v2/en/sport_events/sr:stage:671516/schedule.xml?api_key={your_api_key}") http = Net::HTTP.new(url.host, url.port) http.use_ssl = true http.verify_mode = OpenSSL::SSL::VERIFY_NONE request = Net::HTTP::Get.new(url) response = http.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.sportradar.com") conn.request("GET", "/indylights/trial/v2/en/sport_events/sr:stage:671516/schedule.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.com/indylights/trial/v2/en/sport_events/sr:stage:671516/schedule.xml?api_key={your_api_key}" ``` > The above command returns xml structured like this. Access the Stage Schedule feed by replacing the parameters in the following URL: https://api.sportradar.com/indylights/`{access_level}`/`{version}`/`{language_code}`/sport_events/`{stage_id}`/schedule.`{format}`?api_key=`{your_api_key}` | Parameter | Description | | --------- | ----------- | | `access_level` | Defines the access level of your API key as Production (production) or Trial (trial). | | `version` | Version number of the API you are accessing (Current Version: v2). | | `language_code` | 2 letter code for supported languages: en (English). | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Stage Summary Provides schedules and results information based on the stage provided (season, event, practice, qualifying, or race).
Note: Results returned in a Summary endpoint will vary depending on the type of stage provided (season, event, practice, qualifying, qualifying part, or race).
View our extended documentation for details or open the links in the right sidebar for samples.
Update Frequency: As Necessary
Content Type: Raw XML or JSON
Category & Sport Information Data Points: Category Id
Category Name
Sport Id Sport Name
Competitor Information Data Points: Gender Id Name
Stage Information Data Points: Description
Disabled
Scheduled
Scheduled End
Single Event
Stage Id
Type
Results Information Data Points: Best Speed
Car Number
Fastest Lap Time
Gap/Time
Grid
Laps
Podiums
Points
Pole Positions
Position
Races
Races with Points
Speed
Status
Top 10
Top 5
Victories
Venue Information Data Points: City
Coordinates
Country
Country Code
Curves Left
Curves Right
Debut
Id
Length
Name
Official URL
Timezone
```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.com/indylights/trial/v2/en/sport_events/sr:stage:708616/summary.xml?api_key={your_api_key}") http = Net::HTTP.new(url.host, url.port) http.use_ssl = true http.verify_mode = OpenSSL::SSL::VERIFY_NONE request = Net::HTTP::Get.new(url) response = http.request(request) puts response.read_body ``` ```python import http.client conn = http.client.HTTPSConnection("api.sportradar.com") conn.request("GET", "/indylights/trial/v2/en/sport_events/sr:stage:708616/summary.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.com/indylights/trial/v2/en/sport_events/sr:stage:708616/summary.xml?api_key={your_api_key}" ``` > Click here for a Summary sample of a Sport. > Click here for a Summary sample of a Season. > Click here for a Summary sample of an Event. > Click here for a Summary sample of a Practice. > Click here for a Summary sample of a Qualifying stage. > Click here for a Summary sample of a Race. Access the Stage Summary feed by replacing the parameters in the following URL: https://api.sportradar.com/indylights/`{access_level}`/`{version}`/`{language_code}`/sport_events/`{stage_id}`/summary.`{format}`?api_key=`{your_api_key}` | Parameter | Description | | --------- | ----------- | | `access_level` | Defines the access level of your API key as Production (production) or Trial (trial). | | `version` | Version number of the API you are accessing (Current Version: v2). | | `language_code` | 2 letter code for supported languages: en (English). | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | Return to top ## Frequently Asked Questions

Q: How does the stage system work?

A: The Indy Lights API uses generic stage implementation. The core of the API is built around the concept of stages. For example, an event contains the following stage types: practice, qualifying, and race. Each of those stages, in turn, have stages (except Practice which has no sub-stages). The IDs of each stage are usable in the URL path to request information about that particular stage.

The Indy Lights sport and seasons within it are stages as well. The sport stage consists of season stages for each annual season. Using the ID of a chosen season as a parameter in the Stage Summary endpoint you can "drill down" into each season. For example, using the 2022 season ID as a parameter in the Stage Summary endpoint, the sub-stages will be individual race events. From the race event, you can drill down into the practice, qualifying, and race stages using the same endpoint with different stage IDs.

The best way to 'start' the navigation with the Indy Lights API is using the Seasons endpoint. From there one can obtain the stage ID for the season required and use that as a parameter in the Stage Summary endpoint.

Stage Type Information Included Sub-stages
Sport Information about the seasons included. Note probabilities do not return valid data on this stage. Indy Lights seasons.
Season Contains the season schedule, driver standings and statistics. Events on the race calendar for that season.
Event Information about a single event, the competitors, the teams, and the circuit. Sessions (eg: Practice, Qualifying, Race)
Practice Competitors and results of practice such as fastest time etc. None
Qualifying Information pertaining to the qualifying stage of the event including conditions, competitors, and overall qualifying results. Qualifying Parts
Race Details of the race itself, including the competitors and overall results. Laps

Q: What is the Date format?

A: We present date only values in the ISO 8601 standard format.
ex: 2013-04-03
We use these for attributes that have date and no time (such as birthdate). For more information: https://en.wikipedia.org/wiki/ISO_8601

Q: What time zone are the date time fields presented in?

A: All of our Date/Time attributes are in UTC, presented in the ISO 8601 standard format.
ex: 2013-04-03T18:15:00+00:00
For more information: https://en.wikipedia.org/wiki/ISO_8601

Q: What races are covered in the Indy Lights API?

A: For a detailed breakdown of races covered, reference our Coverage Matrix.

Q: What are the stage types I can expect to see in the feeds?

A: Here are the Indy Lights stage:

  • sport
  • season
  • event
  • practice
  • qualifying
  • race

Q: How do I know what "stage" I am currently looking at?

A: Each stage has a "stage" element. The stage element has an attribute "type" which displays the stage type. The different valid stage types are listed above.

Q: How do I retrieve information about an individual driver?

A: Use the Competitor Profile endpoint with the required driver's competitor ID. The best place to get the driver's competitor ID is the Stage Summary endpoint, using the season stage ID.

Q: Is it updated in real-time?

A: No, post-event. Meaning results of practice are available after practice session is complete, similarly for qualification sessions and the race itself.

Q: Does this API include Qualifying and Practice sessions?

A: Yes, qualifying and practice sessions are updated post-event.

Q: What are the possible statuses of a race or stage?

A: Here are the possible stage statuses and their definitions:

  • Cancelled - The stage is cancelled and will not be taking place
  • Closed - The stage is over and we have validated the results
  • Completed - The stage is over, but we have not finished data collection and validation
  • Finished - The stage is over
  • Not Started - The stage has not begun
  • Preliminary - The stage is about to begin
  • Running - The stage is currently in progress

Q: What are the possible result statuses?

A: Here are the possible result statuses:

  • Finished
  • Out
Return to top

Docs Navigation