IndyCar v2

Frequently Asked Questions
API API Version
IndyCar v2
Note: Authentication is required for all API calls.
## IndyCar v2 API Map To best utilize the IndyCar 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 win probabilities for a given race: >
  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 for the upcoming race
  4. Call the Stage Probabilities using the 'race' Stage Id
  5. Within the results locate the win probability for each racer
>The probability of a win for each racer is displayed. 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 profile feeds. ## Competitor Profile Provides biographical information for a given driver. ```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.us/indycar/trial/v2/en/competitors/sr:competitor:8101/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.us") conn.request("GET", "/indycar/trial/v2/en/competitors/sr:competitor:8101/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.us/indycar/trial/v2/en/competitors/sr:competitor:8101/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.us/indycar/`{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` | Optional 2 letter code for supported languages: en (English), ru (Russian), and zh (simplified Chinese). | | `competitor_id` | Id of a given competitor. | | `format` | xml or json. | | `your_api_key` | Your API key. | To retrieve the XML Schema Definition (.XSD) for the Competitor Profile, use the following URL. http://schemas.sportradar.com/bsa/genericstage/v2/xml/endpoints/genericstage/competitor_profile.xsd Return to API map ## Seasons Provides a complete historical list of available seasons. This is the starting point for the IndyCar API. ```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.us/indycar/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.us") conn.request("GET", "/indycar/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.us/indycar/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.us/indycar/`{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` | Optional 2 letter code for supported languages: en (English), ru (Russian), and zh (simplified Chinese). | | `format` | xml or json. | | `your_api_key` | Your API key. | To retrieve the XML Schema Definition (.XSD) for the Seasons, use the following URL. http://schemas.sportradar.com/bsa/genericstage/v2/xml/endpoints/genericstage/seasons.xsd Return to API map ## Stage Probabilities Provides the outrights for each driver for a given race. ```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.us/indycar/trial/v2/us/sport_events/sr:stage:351963/probabilities.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.us") conn.request("GET", "/indycar/trial/v2/us/sport_events/sr:stage:351963/probabilities.xml?api_key={your_api_key}") res = conn.getresponse() data = res.read() print(data.decode("utf-8")) ``` ```shell curl -X GET "https://api.sportradar.us/indycar/trial/v2/us/sport_events/sr:stage:351963/probabilities.xml?api_key={your_api_key}" ``` > The above command returns xml structured like this. Access the Stage Probabilities feed by replacing the parameters in the following URL: https://api.sportradar.us/indycar/`{access_level}`/`{version}`/`{language_code}`/sport_events/`{stage_id}`/probabilities.`{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` | Optional 2 letter code for supported languages: en (English), ru (Russian), and zh (simplified Chinese). | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | To retrieve the XML Schema Definition (.XSD) for the Stage Probabilities, use the following URL. http://schemas.sportradar.com/bsa/genericstage/v2/xml/endpoints/genericstage/probabilities.xsd Return to API map ## Stage Schedule Provides the schedule for a given stage. ```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.us/indycar/trial/v2/en/sport_events/sr:stage:348851/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.us") conn.request("GET", "/indycar/trial/v2/en/sport_events/sr:stage:348851/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.us/indycar/trial/v2/en/sport_events/sr:stage:348851/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.us/indycar/`{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` | Optional 2 letter code for supported languages: en (English), ru (Russian), and zh (simplified Chinese). | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | To retrieve the XML Schema Definition (.XSD) for the Stage Schedule, use the following URL. http://schemas.sportradar.com/bsa/genericstage/v2/xml/endpoints/genericstage/schedule.xsd Return to API map ## Stage Summary Provides stage and result information for each competitor and team. ```ruby require 'uri' require 'net/http' require 'openssl' url = URI("https://api.sportradar.us/indycar/trial/v2/en/sport_events/sr:stage:348851/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.us") conn.request("GET", "/indycar/trial/v2/en/sport_events/sr:stage:348851/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.us/indycar/trial/v2/en/sport_events/sr:stage:348851/summary.xml?api_key={your_api_key}" ``` > The above command returns xml structured like this. Access the Stage Summary feed by replacing the parameters in the following URL: https://api.sportradar.us/indycar/`{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` | Optional 2 letter code for supported languages: en (English), ru (Russian), and zh (simplified Chinese). | | `stage_id` | Id of a given stage. | | `format` | xml or json. | | `your_api_key` | Your API key. | To retrieve the XML Schema Definition (.XSD) for the Stage Summary, use the following URL. http://schemas.sportradar.com/bsa/genericstage/v2/xml/endpoints/genericstage/summary.xsd Return to API map ## Frequently Asked Questions

Q: What format are date fields presented in?

A: When we present date only values we present these 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 format 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: How does the stage system work?

A: The IndyCar 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. Qualifying stages contain sub-stages known as "Qualifying Parts". In the Race stages, the sub-stages are laps. You can use the lap stage ID in the URL to get specific lap details, including driver times, and position.

The IndyCar 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 2018 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, race, and lap stages of a race using the same endpoint with different stage IDs.

The best way to "start" the navigation with the IndyCar 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. Which is limited to the current and previous season only. Note probabilities do not return valid data on this stage. IndyCar seasons: 2017, 2018.
Season Contains the season schedule, driver standings and statistics. Events on the IndyCar 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
Qualifying Part Information about the individual qualifying parts of the overall qualifying stage such as conditions, competitors, and results. None
Race Details of the race itself including the competitors, lap by lap, and overall results. Laps
Lap Specific details on individual laps such as driver positions, times, etc. Note probabilities do not return valid data on this stage. None.

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

A: Here are the IndyCar stage:

  • sport
  • season
  • event
  • practice
  • qualifying
  • qualifying_part
  • race
  • lap

Q: How do I see the Championship points table?

A: Use the stage summary endpoint and a season stage ID as the parameter. The competitors node lists competitors, ranked with points, position, victories, races, races with points, and podiums.

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" displays stage type. The different valid stage types are listed above.

Q: How do I get the probabilities for the entire Championship? Or only one race?

A: You can use season, event, and race stage IDs as parameters for the probabilities endpoint. Probabilities are available for the individual driver to win the season, a single event, and race stage. Probabilities are not available on the Sport, Practice, Qualifying, or Lap stages.

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: What races are covered in the IndyCar API?

A: The entire IndyCar Championship.

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 race and stage statuses:

  • cancelled
  • finished
  • not_started
  • completed
  • closed
  • preliminary

Q: What are the possible result statuses?

A: Here are the possible result statuses:

  • Finished
  • Out
Return to top

Docs Navigation